UNIT 2 PART B

1)b)Sketch in detail about the requirement analysis with a suitable diagram.

REQUIREMENTS ANALYSIS
– Requirement analysis is a significant and essential activity after elicitation.
– We analyze, refine, and scrutinize the gathered requirements to make consistent and
unambiguous requirements.
– This activity reviews all requirements and may provide a graphical view of the entire
system.
– After the completion of the analysis, it is expected that the understandability of the project
may improve significantly.
– Here, we may also use the interaction with the customer to clarify points of confusion and
to understand which requirements are more important than others.

The various steps of requirement analysis are shown in fig:

(i) Draw the context diagram:

– The context diagram is a simple model that defines the boundaries and interfaces of the
proposed systems with the external world.
– It identifies the entities outside the proposed system that interact with the system.
– The context diagram of student result management system is given below:
(ii) Development of a Prototype (optional):
– One effective way to find out what the customer wants is to construct a prototype,
something that looks and preferably acts as part of the system they say they want.

– We can use their feedback to modify the prototype until the customer is satisfied
continuously. Hence, the prototype helps the client to visualize the proposed system and
increase the understanding of the requirements. When developers and users are not sure
about some of the elements, a prototype may help both the parties to take a final decision.

– Some projects are developed for the general market. In such cases, the prototype should
be shown to some representative sample of the population of potential purchasers. Even
though a person who tries out a prototype may not buy the final system, their feedback
may allow us to make the product more attractive to others.

– The prototype should be built quickly and at a relatively low cost. Hence it will always
have limitations and would not be acceptable in the final system. This is an optional
activity.

(iii) Model the requirements:

– This process usually consists of various graphical representations of the functions, data
entities, external entities, and the relationships between them.
– The graphical view may help to find incorrect, inconsistent, missing, and superfluous
requirements.
– Such models include the Data Flow diagram, Entity-Relationship diagram,
Data Dictionaries, State-transition diagrams, etc.

(iv) Finalise the requirements:

– After modeling the requirements, we will have a better understanding of the system
behavior.
– The inconsistencies and ambiguities have been identified and corrected.
– The flow of data amongst various modules has been analyzed.
– Elicitation and analysing activities have provided better insight into the system.
– Now we finalize the analyzed requirements, and the next step is to document these
requirements in a prescribed format.
Requirements Modeling Approaches
Each element of the requirements model represented in the following figure presents the
problem from a different point of view.
●​ Scenario-based elements
depict how the user interacts with the system and the specific sequence of activities
that occur as the software is used.
●​ Class-based elements
model the objects that the system will manipulate, the operations that will be applied
to the objects to effect the manipulation, relationships between the objects, and the
collaborations that occur between the classes that are defined.
●​ Behavioral elements
depict how external events change the state of the system or the classes that reside
within it.
●​ Flow-oriented elements
represent the system as an information transform, depicting how data objects are
transformed as they flow through various system functions.

2)b)Design the following UML diagrams for EXAM REGISTRATION.

A sequence diagram shows an interaction arranged in time sequence. It shows objects

participating in interaction by their lifeline by the message they exchange arranged in time
sequence. Vertical dimension represent time and horizontal dimension represent object

A collaboration diagram, also called a communication diagram or interaction diagram, A

collaboration diagram resembles a flowchart that portrays the roles, functionality and
behavior of Individual objects as well as the overall operation of the system in real time. The
collaboration diagram is to show how the Student registers and the authorities maintain the
details of the registered students in the Information system. Here the sequence is numbered
according to the flow of execution.
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. activity diagrams can be used to
describe the business and operational step-by-step workflows of components in a system. An
activity diagram shows the overall flow of control. An activity is shown as a rounded box
containing the name of the operation.
3)b)Design the following UML diagrams for Student Information System.
A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between
systems and users in a particular environment and related to a particular goal. It is represented
using ellipse.Actor is any external entity that makes use of the system being modeled

A class is drawn as rectangle box with three compartments or components separated by

horizontal lines. The top compartment holds the class name and middle compartment
holds the attribute and bottom compartment holds list of operations.
4)b)Explain briefly about class based modeling.

classes:A class is a blueprint or prototype that defines the attributes (data) and methods
(behaviors) for objects. It represents the structure and capabilities of objects belonging to the
same type. Example: A Car class might have attributes like brand, model, and color, and
methods like start(), stop(), and accelerate().

Objects: Objects are instances of classes, representing individual entities with specific
attributes and behaviors. Each object has its own state (attribute values) and can perform
actions (method calls). Example: If Car is a class, objects could be car1 with brand =
"Toyota" and car2 with brand = "Honda". Each car object behaves independently.

Attributes:
Definition: Attributes are the properties or data members of a class. They represent the
characteristics or data that an object of the class can hold.
Purpose: Describe the state or information about the class.

Operations
Definition: Operations are the methods or functions that define the behavior of the class.
They represent what an object of the class can do or how it interacts.
Purpose: Specify the functionality or actions the class can perform.
PACKAGE DIAGRAM:
A package diagram is represented as a folder shown as a large rectangle with a top attached to
its upper left corner. A package may contain both sub ordinate package and ordinary model
elements. A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a grouping of
elements in the OO model, and is a Cradle extension to UML. PDs can be used to show
groups of classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs). There are three
types of layer. They are
o User interface layer
o Domain layer
o Technical services layer

COLLABORATION DIAGRAM:
A collaboration diagram, also called a communication diagram or interaction diagram, a
sophisticated modeling tool can easily convert a collaboration diagram into a sequence
diagram and vice. A collaboration diagram resembles a flowchart that portrays the roles,
functionality and behavior of Individual objects as well as the overall operation of the system
in real time.
PART B
Sketch the UML diagrams for library management system
A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between
systems and users in a particular environment and related to a particular goal. It is represented
using ellipse.Actor is any external entity that makes use of the system being modeled

A class is drawn as rectangle box with three compartments or components separated by

horizontal lines. The top compartment holds the class name and middle compartment
holds the attribute and bottom compartment holds list of operations.

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. activity diagrams can be used to
describe the business and operational step-by-step workflows of components in a system. An
activity diagram shows the overall flow of control. An activity is shown as a rounded box
containing the name of the operation.
Q. No Questions

QA201 Define Requirement analysis.

Requirement analysis provides the appropriate mechanism for understanding

what the customer wants, analyzing need, assessing feasibility, negotiating a
reasonable solution, specifying the solution unambiguously, validating the
specification, and managing the requirements as they are transformed into an
operational system

QA202 Define the term Elicitation.

It certainly seems simple enough—ask the customer, the users, and others what the
objectives for the system or product are, what is to be accomplished, how the
system or product fits into the needs of the business.

QA203 What are the types related to behavioral diagrams?

Sequence Diagram

Collaboration Diagram

QA204 Consider an ATM system. Identify at least three different actors that interact
with this system.

User

ATM system

Bank Server

QA205 What is known as SRS review? How is it conducted?

SRS is a document that is created by the development team in collaboration

with Business Analysts and environment/data teams. Typically, this document
once finalized will be shared with the QA team via a meeting where a detailed
walkthrough is arranged.

QA206 What is meant by software prototyping?

Software prototyping is the activity of creating prototypes of software

applications, i.e., incomplete versions of the software program being
developed
QA207 Define Behavioral Mode?

Behavioral model is specially designed to make us understand behavior and

factors that influence behavior of a System

QA208 Sketch the tools used in class diagram.

Class diagrams are not only used to visualize the static view of the system but
are also used to construct the executable code for forward and reverse
engineering of any system. The class diagram clearly shows the mapping with
object-oriented languages such as Java, C++, etc.