PROJECT ENGINEERING REQUIREMENT ANALYSIS MODELING

ANALYSIS CONCEPTS & PRINCIPLES

  1. The information domain must be represented and understood.
  2. The function must be defined.
  3. The behavior of software must be represented.
  4. Models that depict information, function, and behavior must be segregated in a manner that uncovers details in a layered manner.
  5. The analysis process must move from essential information to implementation details.

FUNCTIONAL MODELLING: It provides the outline that what the system is supposed to do. It does not describe what is the need o evaluation of data, when they are evaluated, and how they are evaluated apart from all it only represents the origin of data values. It describes the function of the internal process with the help of DFD (Data Flow Diagram).

INFORMATION FLOW MODELING: It distinguishes the discrete processing stage within the process, and describes how information flows through the system.

BEHAVIOR MODEL: It is specially designed to make us understand behavior and factors that influence the behavior of a system. the behavior of a system is represented by a State Transition Diagram (STD). It is a collection of states and events.

Comments

Post a Comment

Popular posts from this blog

DESIGN PRINCIPLES

PROBLEM PARTITIONING: Divide the problem and conquer the problem it means to divide the problem into smaller pieces so that each can be captured separately. ABSTRACTION: The process of hiding certain details and showing only essential information to the user. MODULARITY: It specifies the division of software into separate modules which are differently named, addressed, and integrated later on in to obtain completely functional software. STRATEGY OF DESIGN: To design a system, there are two possible approaches- Top-Down Approach: main components and then sub-components designed Bottom-Up Approach: sub-components and then integrate them to obtain the main component.
Read more

COMPONENT ASSEMBLY MODEL

This model follows an object-oriented methodology where the whole system is divided into components, if they are already available in the library then we import them else we have to build them and at last, we construct the system by integrating them. CHARACTERISTICS: Use of object-oriented technology. Component-class that encapsulates both data and algorithm. Component delivered to be reusable. Paradigm similar to spiral model, but engineering activity involves components. The system is produced by assembling the correct components. ADVANTAGES: Time and resource conservative. Having object-oriented methodology. Components are built once and then they can be reused further. Suitable for small to large object-oriented projects. Very low cost in the construction of the system. DISADVANTAGES: Can’t use it for pioneering projects. Needs good planning and design. Needs a clear and complete definition of the whole system before dividing it into components. Need experts to divide the syst...
Read more

SOFTWARE TESTING

Image
It is a process of verifying and validating that software or application is bug-free, meets the technical requirements as guided by its design and development, and meets the user requirements effectively and efficiently with handling all the exceptional and boundary cases. SOFTWARE TESTING STRATEGIES VERIFICATION: It refers to the set of tasks that ensure that software correctly implements a specific function. VALIDATION: It refers to a different set of tasks that ensure that the software that has been built is traceable to customer requirements. Verification -> “Are we building the product right?” Validation -> “Are we building the right product?” TYPES OF SOFTWARE TESTING MANUAL TESTING: Manual testing includes testing software manually which means without using any automated tool or any script. The tester takes over the role of an end-user and tests the software to identify any unexpected behavior or bug. There are different stages for manual testing suc...
Read more