1. Group iv MBARARA UNIVERSITY OF SCIENCE AND TECHNOLOGY INSTITUTE OF COMPUTER SCIENCE DEPARTMENT OF COMPUTER SCIENCE COURSE: BACHELOR OF COMPUTER SCIENCE COURSE UNIT: SOFTWARE DESIGN AND DEVELOPMENT COURSE CODE: CSC1200 LECTURER: MUGONZA ROBERT YEAR: 2013/2014

2. GROUP 4 1. 1.KABUGHO DOREEC 2013/BCS/002 2. NIMWESIGA GERALD 2013/BCS/041/PS 3. TUSHABE SEZI 2013/BCS/091/PS 4. ATUKUNDA ALLAN 2013/BCS/012/PS 5. NIWAMANYA DANDY 2013/BCS/026/PS 6. TUKAHEBWA BENARD 2013/BCS/101/PS 7. KALENDE REBECCA 2013/BCS/081/PS 8. MUHANGUZI BRIGHTON 2013/BCS/021/PS 9. IRAGUHA RICHARD 2013/BCS/114/PS 10. ATUHAIRWE CHRISTINE 2013/BCS/023/PS 11.NUWATUMANYA AUTHUR 2013/BCS/016/PS

3. Moving target It is where the client changes his or her requirements during the software development process.

4. Requirements A requirement describes a condition or capability to which a system must conform; In systems engineering, a requirement can be a description of what a system must do. Requirements are descriptions of the services that a software system must provide and the constraints under which it must operate Requirements can range from high-level abstract statements of services or system constraints to detailed mathematical functional specifications

5. Types of Requirement User requirements Statements in natural language plus diagrams of the services that the systems provides and its operational constraints. Written for customers System requirements A structured document setting out detailed descriptions of the system services. Written as a contract between client and contractor

6. Software specification A detailed software description which can serve as a basis for a design or implementation. Written for developers

7. Requirements traceability Requirements traceability is a sub-discipline of requirements management within software development and systems engineering.requirements managementsoftware developmentsystems engineering Requirements traceability is concerned with documenting the life of a requirement and providing bi-directional traceability between various associated requirements. It enables users to find the origin of each requirement and track every change that was made to this requirement. For this purpose, it may be necessary to document every change made to the requirement. It has been argued that even the use of the requirement after the implemented features have been deployed and used should be traceable.

8. Requirements Traceability cont’d Requirements Traceability is concerned with documenting the relationships between requirements and other development artifacts. Its purpose is to facilitate: the overall quality of the product (s) under development the understanding of product under development and its artifact; and the ability to manage change.

9. Software development process A software development process, also known as a software development lifecycle, is a structure imposed on the development of a software product. developmentsoftware

10. Agile Development Agile Development –Agility means to have a process in place that will allow us (and urge us) to react on changing business requirements as soon as possible: –To accept that the project's goal is a moving target. Agile means adopting an approach to IT that emphasizes flexibility, responsiveness to change and innovation. –This is achieved through modular and iterative development based on user involvement and feedback:

11. Agile Development cont’d Compared with traditional tools and methods, agile offers a fundamentally different approach to tackling business problems. Instead of trying to lock down requirements and minimize changes up-front, agile encourages continuous experimentation, improvement and reprioritization. The approach to user involvement also differs fundamentally.

12. Agile Development comparison with a traditional Waterfall The traditional approach like a strict Waterfall model, after each phase is finished, it proceeds to the next one. Reviews may occur before moving to the next phase which allows for the possibility of changes (which may involve a formal change control process). Reviews may also be employed to ensure that the phase is indeed complete; the phase-completion criteria are often referred to as a "gate" that the project must pass through to move to the next phase. Waterfall discourages revisiting and revising any prior phase once it's complete. But agile encourages a modular approach using short iterations to learn and adapt.

13. Agile Development cont’d The traditional approach favors heavy user engagement up-front to determine and lock down detailed specifications and at the end to test the final product. In contrast, agile embeds users in the process for the duration of the project, making them an integral part of the development team rather than a company to be consulted.

14. Software process is the activities involved in the development of the software. Software development process also known as SDLC is a structure imposed on the development of a software product as in embedded real time system based on Siemens 8 automation. Siemens private communication system (PN) has invested in the software process methods of formal inspections, measurements and the project management training. Here are the software process improvement methods used by some of the companies: SIA found in Johnson City, TN used SEPG, CASE, measurements, ISO 9000. SME which is found in Danvers MA used inspection, measurement and process definition

15. QN 2….NO 2 An organization whose goal is to reduce development cycle time should have a high visible measurement of project development schedule time like (3-5) years. Since the selected sites are all involved with the maintaining the mature products as well as developing newer versions of these products. Data collection and analysis can be observed by comparing performance measures calculated for the current development as compared with prior development provided they are doing the work of similar difficulty, as observed development as usual called releases, projects or products with the development organizations. The baseline data should initially be collected for the last major product software release that has been used by the customers in the field for at least one year. Tracking of similar resulting from the previously shared software measurements training across Siemens business units. Identification of the defects found per phase and in total should be countered and debugged in generalized phases, implementations phases which begin when an approved functional specifications is available and a high level design has begun, qualification