Presentation on theme: "L ECTURE 6 – R EQUIREMENT A NALYSIS System Requirements Requirements Analysis Techniques Software Project Management Maria Petridou 1."— Presentation transcript:
L ECTURE 6 – R EQUIREMENT A NALYSIS System Requirements Requirements Analysis Techniques Software Project Management Maria Petridou 1
S YSTEM R EQUIREMENTS System Requirements are all of the capabilities that the new system must have. Software Project Management 2 Maria Petridou The systems request produced in the planning phase lists the high- level business requirements of the proposed system. From Planning Phase
S YSTEM R EQUIREMENTS Software Project Management 3 Maria Petridou Analysis Phase The first step in the analysis phase is to develop an analysis strategy in order to define the system requirements. The aim is to turn the precise business requirements into precise system requirements.
S YSTEM R EQUIREMENTS Software Project Management 4 Maria Petridou The purpose of defining requirements is to provide information for the next steps in the analysis phase (use cases, process model, data model, etc.) and to define the scope of the system. The analysis phase involves: 1. Understanding current system 2. Identifying improvements 3. Define requirements for new system
S YSTEM R EQUIREMENTS Software Project Management 5 Maria Petridou Stakeholders and system analysts should work in co-operation in order to determine the system requirements. Stakeholders – users, sponsors, technical staff. An analysis strategy consists of requirements analysis techniques and information gathering techniques. System requirements are divided in Functional: Activities the system MUST perform. ( Information & Process) Non-functional: Characteristics of the system other than activities ( Performance, Operational, Security, Cultural, Political)
S YSTEM R EQUIREMENTS Software Project Management 6 Maria Petridou Exercise 1: Determine which in the following are functional requirements and which ones are non-functional requirements. (Dennis&Wixom, Ch.4). - Be accessible to web users - Include the company standard logo and colour scheme - Restrict access to profitability information - Provide management reports - Have 2-second maximum response time for predefined queries, and 10- minute maximum response time for ad-hoc queries. - Include sales information that is updated at least daily. - Print additional reports in other languages. - Include actual and budgeted cost information.
R EQUIREMENTS A NALYSIS T ECHNIQUES Software Project Management 7 Maria Petridou Main requirements analysis techniques are the following: Business process automation (BPA) The basic way in which the organisation operates is left unchanged and computer systems are used to automate some of the work. Focus on automate processes. No changes to organisation. Business process improvement (BPI) Moderate changes to the way in which the organisation operates in order to achieve improvements. Focus on improve processes. Moderate changes to organisation. Business process re-engineering (BPR) Uses new ideas and technology to make major changes to the way in which the organisation operates. Focus on innovation. Major changes to organisation.
R EQUIREMENTS A NALYSIS T ECHNIQUES Software Project Management 8 Maria Petridou Some other requirement analysis techniques are:
R EQUIREMENTS A NALYSIS T ECHNIQUES Software Project Management 9 Maria Petridou
R EQUIREMENTS A NALYSIS T ECHNIQUES Software Project Management 10 Maria Petridou
R EQUIREMENTS A NALYSIS T ECHNIQUES Software Project Management 11 Maria Petridou Each requirements analysis technique has different impact on the project: Reading: (Dennis&Wixom, chapter 4).