Notes for BSc CSIT

There are mainly three categories of risks that are likely to arise in software projects. They are described below:-: 1) Product Risk: Product risks are the risks that influence the quality attributes as well as the performance of software being developed. Example: failure of purchase component to perform as expected 2) Project Risk: Project risks are the risks that influence the schedule of a software project and that if occur delay the development process. Example: staff turnover, hardware unavailability, etc. 3) Business Risk: Business risk is a risk that affects the organization's business that is developing or procuring the software. it could be anything that has the potential of threatening the generation of profits at the predetermined target levels. Business risks could be quite dangerous for the long-term sustainability of the business. Example: Technology change, Product completion, etc. Risk Analysis Stage - Risk Analysis in project management is a sequence of process

 We need formal specification because:- -  Formal Specification involves investing more effort in the early phases of software development.  - To explain why formal specification techniques help to discover problems in system requirements. - To describe the use of:-   ° algebraic technique(for interface specification) &   °  model-based techniques( for behavioral specification) - To introduced Abstract State Machine Model(ASMM) - Formal Specification reduces requirements error as it forces a detailed analysis of the requirements.   Behavioral specification - Behavioral specification describes constraints on the behavior of the implementation. - Example:- functionality, safety, security, performances. - Algebraic specification can cumbersome when the object operations are not independent of the object state. - Model-based specification exposes the system state and defines the operations in terms of changes to that state. - The Z notation is a mature technique for model-based specifi