Software Engineering Question Bank Solution 2076

Explain system modeling with suitable example.

System modeling is the process of creating abstract representations of a system to understand,
design, analyze, and communicate its various aspects. Models provide a visual and conceptual
understanding of the system’s structure, behavior, and interactions, helping stakeholders comprehend and validate system requirements. One of the commonly used techniques for system modeling is Unified Modeling Language (UML).

Example of System Modeling: Let’s consider the development of an online movie ticketing system

1. Use Case Diagram:
   A use case diagram in UML represents the interactions between actors (users or external systems) and the system. In this case, the actors could be customers, administrators, and the payment gateway. The use case diagram would illustrate various functionalities, such as “Search for books,” “Add to cart,” “Make a purchase,” “Manage inventory,” and “Generate sales report.” These use cases help identify the different user interactions and the system’s responses.
2. Sequence Diagram:
   A sequence diagram describes the interactions between different objects in a sequential manner. In the context of the online bookstore system, a sequence diagram could illustrate the steps involved in a customer making a purchase. It would show the interactions between the “Customer” object, the “Order” object, and the “Payment” object, highlighting the sequence of events.

What is software process model? Discuss waterfall model with its merits and demerits.

A software process model is a structured approach used to guide and manage the software development process. It defines a set of activities, phases, and deliverables that need to be accomplished to successfully develop and deliver software. Each process model provides a specific framework to organize tasks, resources, and schedules in a logical manner.

The Waterfall Model: The Waterfall Model is one of the earliest and most straightforward software process models. It follows a sequential and linear approach, where each phase must be completed before moving to the next one. The development process flows from one phase to another in a cascading manner, resembling a waterfall.

fig: Waterfall model

The sequential phases in Waterfall model are :

1. Requirement Gathering and analysis – All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification document.
2. System Design – The requirement specifications from first phase are studied in this phase and the system design is prepared. This system design helps in specifying hardware and system requirements and helps in defining the overall system architecture.
3. Implementation – With inputs from the system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality, which is referred to as Unit Testing.
4. Integration and Testing – All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.
5. Deployment of system – Once the functional and non-functional testing is done; the product is deployed in the customer environment or released into the market.
6. Maintenance – There are some issues which come up in the client environment. To fix those issues, patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

Merits of Waterfall model

• This model is simple to implement also the number of resources that are required for it is minimal.
• Requirements are simple & explicitly declared. They remain unchanged during entire project
  development.
• The start and end points for each phase is fixed, which makes it easy to cover progress.
•  It gives easy to control and clarity for the customer due to a strict reporting system.
• Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a review process.

Demerits of Waterfall model

• No working software is produced until late during the life cycle.
• In this model, the risk factor is higher, so this model is not suitable for more significant and complex projects.
• This model cannot accept the changes in requirements during development.
• It becomes tough to go back to the phase.
• Since the testing done at a later stage, it does not allow identifying the challenges and risks in the earlier phase, so the risk reduction strategy is difficult to prepare.

Discuss different types of risks which are likely to arise in software projects. Briefly explain risk analysis stage during risk management process.

false

Briefly explain functional, non-functional, and domain requirements.

false

What are rapid prototyping techniques? Briefly explain different rapid prototyping techniques

false

What is formal specification? Discuss interface specification in detail.

false

What are the activities of architectural design process? Discuss abstract machine model.

false

What is modular decomposition? Discuss object oriented model of decomposition.

false

Discuss the importance of use case diagram in object-oriented development. Draw a use case diagram for library system.

false

What is clean room software development? Discuss the characteristics of cleanroom software development.

false

Discuss path testing with suitable example.

false

Write Short notes on:
a. Reliability validation
b. Reverse engineering

false