Software Lifecycle

  • November 2019
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Software Lifecycle as PDF for free.

More details

  • Words: 417
  • Pages: 2
Life cycle model Transport Layer Security (TLS) Session Resumption without Server-Side State V-Model- its an extension to the conventionally used waterfall model in the such scenarios, where the primary analysis is over the connection establishment, as design is a very important consideration to start with, it’s the most suited software life cycle with testing provided in every phase. It is clearly visible that each cycle has its own test cases and this enable the periodic testing w.r.t. the individual phases of the cycle.

Operations in different phases of the cycle: 1. Requirement Analysis- Defining the Client and the server nodes where the connection has to be established and the process of TLS resumption of session to be carried out. We also

2.

3.

4.

5.

have to state down the extensions used and all the protocols which have a role in establishment of the connection. System phase- This phase is for the purpose of carrying out the proper usage of resources stated during requirement and to come up with alternatives and techniques for achieving our goal. Here all the data structures which can possibly be implemented in the project have to be dealt with. In the case of ticket construction we make use of structure and enum, which are accompanied with different parameters or field. For security consideration, possibly we can come up with alerts or test conditions to be applied while execution. Architectural design- Here we have to follow the architectural model implemented for ticket construction and distribution. Here we have to come up with integration techniques for all the layers witnessed in our program. We can have a clear idea of all the protocols layering in the model and the establishment of connection between the client, authenticator to the server and its methods. Module design- this is a low level design, in this as the word suggest; we would divide the integral unit into different pieces or modules for separate supervision and a better understand of the program, this would lead to a better coding and programming phase. E.g. here we can give the data types of the fields which would be implement in the structure defined for the ticket extensions and the ticket construction. Coding phase- this would be the phase of devising all the design and arriving at a result thorough the execution or compilation of a code in a compiler. In this case we would be working on C platform, so C compiler would result in coding and execution of the program.

Related Documents

Software Lifecycle
November 2019 20
Staffing Lifecycle
November 2019 15
2 Lifecycle
November 2019 18
Viewstate Ans Lifecycle
October 2019 5