Software engineering
- 2. Topics 1.Change Control Process in Software maintenance . 2.S/w Version Control. 3.Over view of CASE Tools.
- 3. Change control Process in S/w Q.What is change control process? Change control is a systematic approach to managing all changes made to a product or system. Q.What does Change control process ensures? It ensures that the changes to the system are controlled and that their effect on the system can be predicted. Q.When does Change control process comes into effect? It comes into effect when the software and associated documentation are delivered to configuration management change request from which should record the recommendations regarding the change.
- 4. • The recommendations may include assessment of the proposed change, the estimated costs and how the change should be implemented. • This form is submitted to a Change Control Authority (CCA) which decides whether or not the change is to be accepted. If change is approved by the CCA,it is applied to the S/W. What.s Next? • The revised S/W is revalidated by the S/w Quality assurance(SQA) team to ensure that the change has not adversely affected other parts of the S/w. • The changed S/w is handed over to the S/w configuration team and is incorporated in a new version of the system.
- 5. Software Version Control Q.What is Software Version Control process? Version control combines procedure and a tool that manages different versions of configuration items that are created during the S/w engineering process. * In this the detailed record of every version of the s/w must be kept. * This comprises the names of each source code component,including the variations and revisions.
- 6. Version control activities : Divided into 4 main sub-activites. 1.Identify new version: A s/w configuration items(SCI) will receives a new version number when there has been a change to its established baseline. Each previous version will be stored in a corresponding directory such as version1,version2,etc.
- 7. 2.Numbering scheme: The number scheme will have the following format : version x.y.z a. The first letter (X) represents the entire SCI. Therefore changes made to the entire configuration items or changes large enough to warranty a completely new release of items will causes the first digit to increase . b. The second letter (Y) represents a component of SCI. The digit will sequentially increase if a change is made to a component, or small changes to multiple component. c. The third letter(Z) represents a section of components of SCI. This number will only be possible if component of an SCI can be broken down into individual sections.
- 8. 3.Visibility The version number will be visible either in a frame or below the title. The decision for this depends upon the group decision to code all the documents for a frame capable browser or allow for non frame capable browser. In either case, number will always be made available.
- 9. 4.Tracking: The best way to keep track of the different versions is which a version evolution graph. As shown in the figure. figure: Version evolution graph V1.1b V1.1.1 V1.0 V1.1 V1.2 V2.0 V2.1 V1.1a
- 10. Over view of CASE Tools Case tools are software programs that are designed to assist human programmers with the complexity of the processes and the artifacts of software engineering. 1.The use of Computer Aided S/w Engineering(CASE) tool reduces the effort of development, of achieving quality goals and managing change and configuration throughout the product life cycle. 2. Computer Aided S/w engineering (CASE) tools help the project manager, these S/w developer and other key personnel to improve their productivity in the development team.
- 11. Architecture of CASE environment The important component of a modern CASE environment are: 1.User interface. 2.Tool set. 3.Object management system(OMS). 4. A repository 1.USER interface: The user interface provided a consistent framework for accessing the difference tools thus making it easier for the users to interact with the difference tools and hence reducing the learning period.
- 12. 2.Object management system: Different CASE tools represent the s/w product as a set of entities such as specification, design,test data,project plan etc.The object management system maps these logical entities the underlying storage management system(repository). User Interface Tool set Object Management System Repository
- 13. Repository: 1.The complete information about meta-models, methods, project artifacts, baseline,process models etc, is available in the repository. 2. This information can be shared by different team members efficiently thereby improving the project management as a whole. 3. While implementing, the repository can be either cetralized or distributed .Normally this is implemented using a database or a file system.
- 14. Benefits and limitations of CASE tools: Benefits of CASE tools: 1. Improved productivity. 2. Better documentation 3. Reduced lifetime maintenance 4. Improved accuracy 5. Opportunity to non-programmers 6. Intangible benefits. Limitations: 1. Cost 2. Learning curve 3. Tool mix: it is important to make an appropriate selection of tool mix to get cost advantage.
- 15. Most use of CASE tools 1.Software requirements tools: A number of tools are proposed for modeling, tracing,and analyzing requirements . Example: a.Turbo-analyst b.Oracle’s Design/2000,Agro/UML Rational ROSE 2.Software construction: S/w construction tools are the tools which are used to code and implement the s/w and hence transform the s/w requirements into working product. Broadly they can be classified. a.Program editors b. Compilers c. Interpreters d. Debuggers
- 16. 3.S/w maintenance tools: a. Comprehensive tools: These tools are used to assist in human comprehensive and visualization of the programs. Examples are Visual studio,exref etc. b. Re-engineering tool: These are tools which allow the change of existing format i.e a new lnguage or new database or new technology in general. 4. Configuration management: These tools support version control and other activities related to configuration management and control of changes made to the documents. Examples are Clear Case,Change man etc. 5. Project Mangaement: Tools under this category automate size estimations,cost estimation, schedule estimation,risk management activities etc. Some of the tools are MS project,Excel,COCOMO,FPA etc.
- 17. THANK YOU