SYSC 3100 - System Analysis and Design

1. SYSC 3100 - System Analysis and Design Basic Concepts Software lifecycles and Requirement Engineering

2. Questions • How do you build things? • How do you think software is built today? • Are they the same?

3. Objectives • Describe the software life-cycle • Explain the development styles for a small selection of development models. • Waterfall • V • Incremental.

4. Life cycle • A structured set of activities required to develop a software system • Specification; • Design; • Validation; • Evolution. • A software life cycle is an abstract representation of a development process. It presents a description of a process from some particular perspective.

5. Software Life Cycles A software life cycle has a number of: • Distinct activities: “requirements”, “analysis”, “design”, “implementation”, “testing”, “operation” • Products: • requirements, analysis, design and testing documents, • user manual, … • Rules for completing a phase and transitioning to the next phase

6. Software Life Cycles Well-known models for a software life cycle: • The Waterfall model • The V model • Incremental software development • The Rational model (Rational Unified Process)

7. The waterfall model Requirementsdefinition System’s services, constraints and goals System andSoftware Design System architecture, software system functions Implementationand Unit Testing Set of programsor program units Integration andSystem Testing Units and programs areintegrated and tested Operation andMaintenance

8. Waterfall Model Problems • Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements. • Therefore, this model is only appropriate when the requirements are well-understood and changes will be fairly limited during the design process. • Few business systems have stable requirements. • The waterfall model is mostly used for large systems engineering projects where a system is developed at several sites.

9. The V model Requirements Acceptance Testing System Analysis System Testing Unit and IntegrationTesting System Design Implementation

10. Incremental delivery • Rather than deliver the system as a single delivery, the development and delivery is broken down into increments with each increment delivering part of the required functionality. • User requirements are prioritised and the highest priority requirements are included in early increments. • Once the development of an increment is started, the requirements are frozen though requirements for later increments can continue to evolve.

11. Incremental development

12. Incremental development advantages • Customer value can be delivered with each increment so system functionality is available earlier. • Early increments act as a prototype to help elicit requirements for later increments. • Lower risk of overall project failure. • The highest priority system services tend to receive the most testing.

13. (Rational) Unified Software Development Process • A modern process model derived from the work on the UML and associated process. • Inception • is concerned with determining the scope and purpose of the project • establishes the business case for the system • Elaboration • focuses requirements capture and determining the structure/architecture of the system • develops an understanding of the problem domain • Construction: System design, programming and testing • Transition: product installation and rollout

14. Project Phases Workflows Requirements Analysis Design Implementation Test Inception 1 2 3 Size of square relative to time spent on workflow Elaboration 4 5 Construction 6 7 8 Transition 9 10 Iterations within each phase