1.2

• Analysis/Success Criteria is the initial stage where the system analyst identifies problems and defines requirements.
• Design involves creating flowcharts and pseudocode to plan the system's structure and functionality.
• Development is the phase where programmers write and test code.
• Testing involves creating a test plan to evaluate the functionality and identify any errors or bugs.
• Users are the individuals who use the software and provide feedback to the developers.
• Programmers are responsible for writing and testing code and have a median annual salary of $93,000.
• Systems Analysts work with companies to diagnose issues, resolve user problems, and advise on system improvements, earning an annual mean wage of $124,690.
• Testers evaluate software, hardware, and networks for functionality and technical observations.
• Methodology is a process used for developing software, often involving large teams and lasting months or years.
• User requirements are the needs, expectations, and preferences of the people who will use a system.
• End user requirements specify how the system should work.
• Performance requirements focus on how the system delivers specific functions and how it performs.
• Nonfunctional requirements are related to system usability.
• The specification document is a key document produced during the systems life cycle.
• There are three types of specifications: User Requirements specification, Design Specification, and Systems specification.
• The design specification covers how the system should work, its appearance, and user interaction.
• The system specification describes how the project will be carried out.
• Implementation is carried out by programmers and depends on user requirements.
• White box testing checks all pathways through the code, while black box testing focuses on functionality.
• Alpha testing is the final testing by the development team, focusing on whole system functionality and usability.
• Beta testing involves unstructured testing by selected end users on a wide range of hardware and software.
• Acceptance testing- Acceptance testing is the final testing with the intended user(s). It often involves 'scenarios' that the users follow to make sure that the system meets the requirements specification.
• Build- The build phase consists of translating the detailed requirements and design into system components, testing individual elements of usability and preparing for integration and testing for the IT system
• Testing should take place continually during the coding process and include 'destructive testing' to identify program crashes or unexpected behavior.
• Development testing is completed before alpha testing, which is conducted by individuals who have not worked on the code.
• Beta testing is conducted by a small group of users from outside the software company.
• Acceptance testing is the final stage of testing.
• White box and unit testing involve testing the structure of the code.
• Black box testing involves testing the functionality of the code based on requirements.
• Alpha testing is done by the developer or in-house.
• Beta testing is carried out by customers.
• Black box testing is carried out independently of the code used in the program It looks at the program specification and creates a set of test data that covers all the inputs, outputs and program functions
• White box testing depends on the code logic tests are devised which test each path through the code at least once
• Alpha testing - This is carried out by the software developer’s in-house team and by the user. It can reveal errors or omissions in the definition of the system requirements. The user may discover that the system does not do exactly what they wanted
• Beta testing- This is used when commercial software is being developed (e.g. MS Windows, MS Word, Sage Accounts, etc.). The software is given to a number of potential users,

  who agree to use the software and report any faults. Real users may try and do things the developer didn’t anticipate.
• Documentation - Once complete the system must be documented to detail exactly what the system should be able to do. The system design might be documented Technical documentation for use by software engineers. User documentation is a manual that tells users how to operate the designed system. Generally carried out in parallel with installation
• Installation - It is the process of installing a new system like direct changeover, phased changeover, pilot changeover and parallel changeover.
• Evaluation - The user now needs to test every aspect of the software to make sure it does what it is supposed to do. It will be evaluated against the original specification document. This stage is also called Acceptance testing. This includes: requirements, performance, robustness, cost and usability.
• Maintenance - There are three types of maintenance (Corrective, adaptive and perfective)
• Corrective maintenance - Bugs will usually be found when the software is put into action, no matter how thoroughly it was tested.