Notes for BSc CSIT

 Project Planning: Project planning involves breaking down the work into parts and assigning these to project team members, anticipate problems that might arise, and prepare tentative solutions to those problems. The project plan, which is created at the start of a project, is used to communicate how the work will be done to the project team and customers, and to help assess progress on the project. Types of Project plan Validation Plan Configuration management plan Maintenance plan Staff Development Plan 1) Validation plan The validation plan describes the approach, resources, and schedule used for system validation. It is intended to show that the program does what the user requires. 2) Configuration and management plan This plan includes the management of system change. When a system has maintained the role of the CM team is to ensure that changes are incorporated in a controlled way. This plan includes configuration management procedures and structures to be used. 3) Maintenance pl

 Difference between Functional and Non-functional Requirements Functional requirements A functional requirement defines a system or its component. It specifies "What should the software system do?"  A functional requirement is specified by the User. It is mandatory. It is captured in the use case. Defined at a component level. Helps you verify the functionality of the software. Functional Testing like System, Integration, End to End, API testing, etc is done. Usually easy to define. Non-functional requirements A non-functional requirement defines the quality attributes of a software system. It places constraints on "How should the software system fulfill the functional requirements?" A non-functional requirement is specified by technical peoples e.g. Architect, Technical leaders, and software developers. It is not mandatory. It is captured as a quality attribute. Applied to a system as a whole. Helps you to verify the performance of the software. Non-Functional Test