Software Engineering Assesment Report

Running head: SOFTWARE ENGINEERING
SOFTWARE ENGINEERING
Name of the Student
Name of the University
Author Note

SOFTWARE ENGINEERING 1
Table of Contents
Part 1:.........................................................................................................................................2
References:.................................................................................................................................4
Part 2:.........................................................................................................................................5
Strength of Sequence Diagram:.............................................................................................5
Scenario:.................................................................................................................................5
Factors:...................................................................................................................................6
References:.................................................................................................................................6
Part 3:.........................................................................................................................................8
Types of CRUD method and importance:..............................................................................8
References:.................................................................................................................................9
Part 4:.......................................................................................................................................10
Purpose of State Machine Diagram:....................................................................................10
Scenario:...............................................................................................................................10
References:...............................................................................................................................13

SOFTWARE ENGINEERING 2
Part 1:
The analysis class diagram can represent the abstraction of various classes or sub
systems that are included in the design of the system (Deryugina & Nikulchev, 2017). It is the
initial stage for the system. The analysis class diagram shows only the initial classes as it is
an overview of the system. On the other side, the design class diagram is the detailed
overview of the system as the code for the system will be developed on the basis of design
class diagram.
The factors are as follows:
Name: Each of the design pattern will be having a name that will be utilized for the role of
design pattern in the software design.
Problem: It describes the scope of issues that are existed in system design.
Solution: It describes the element structure which can make up the pattern.
Consequences: There are several advantages and disadvantages of the design pattern. The
consequences will concern time trade-offs and spaces (Vanderdonckt & Nguyen, 2019).
Let, there is a wine shop that accept payment in cash, visa card, Amex card and master card.
The analysis class diagram is as follows:

SOFTWARE ENGINEERING 3
Let, assume there is a travel booking company. The design class diagram for the company is
as follows: