System Design and Analysis: Identifying Classes from Use Cases

This report delves into the crucial topic of identifying software classes from use cases within the realm of system design and analysis. The document begins by highlighting the significance of object-oriented modeling as a superior approach to large-scale software design and development, emphasizing its iterative nature. It then proceeds to outline the process of identifying different types of classes, including boundary classes, entity classes, and control classes. The report underscores the importance of Unified Modeling Language (UML) diagrams, particularly use case diagrams, in facilitating this process. Furthermore, it provides insights into the characteristics and roles of each class type, offering practical guidance on how to identify them based on the system's actors, the information they use, and the control logic that governs their interactions. The report concludes by emphasizing the benefits of object-oriented approaches for project management, cost savings, and the avoidance of project delays, making it a valuable resource for students studying system design and software engineering.

Running Head: SYSTEM DESIGN AND ANALYSIS 0
System Design and Analysis
Individual Assignment
Student name

System Design and Analysis 1
Table of Contents
Introduction.................................................................................................................................................2
What is the best way to identify software classes from use cases?.............................................................2
Find boundary classes:.............................................................................................................................2
Find Entity Classes...................................................................................................................................3
Find Control Classes:................................................................................................................................3
Conclusion...................................................................................................................................................4
References...................................................................................................................................................5

System Design and Analysis 2
Abstract
Object-oriented modeling is the best approach for large software designing and development in
the field of software development. It uses iterative approach for identification of classes. In this
report, identification of classes from the use-cases will discuss in next parts. There are different
ways of software development, but Object oriented approach is best approach for managing all
the process of system development. Classes identification is a hard process in object oriented
approach. This report is about identification of software classes.
Keywords: Class, Object, use-cases, and entity.
Introduction
Object oriented approaches are best way to solve a problem in different style. It provides a pre-
solution of a given task with help of tools. It is a programming ways for explaining designing of
project in different styles. There are different diagrams for understanding the flow of
information in the project as well as controls of the project, such as use case diagrams, class
diagrams (Bruegge, 2008).
There are different ways for designing classes from the use-cases. Use-cases are best way to
identify software classes. There are four basic parts of a project are analysis, designing, coding,
and testing. In starting of project, using object-oriented approach, design a flow diagram for
better understanding of a project (Conallen, 2012). There are many advantages of this approach.
This report will discuss about identification of classes in next part of this report. In addition, I
will discuss about the control classes and behavior of the system.
What is the best way to identify software classes from use cases?
Unified Modeling Language (UML) is an object oriented based approach for development
softwares. It has different diagrams for showing functional requirements of a project, such as use
case diagram, class diagram, and others. It is so difficult to design classes from use cases. There
are different ways for identify software classes from use cases. It is possible by software as well
as from step to step analyzing different cases from requirement. It is so necessary that each

System Design and Analysis 3
requirement is fulfill, which is the vendor provides. There are so many basic tools for finding
classes from requirement, such as Eiffel studio for project management. (Gomaa, 2011)
First step for finding classes is analyze behavior of described use cases. There are different
classes present in the use cases, such as boundary classes, entity classes, and control classes.
Best way to find classes is based on three perspectives of the system, which are actors,
information used by system, and system control logic. Identification of classes means, it should
be described by name in some sentences (Jacobson, 1993).
Find boundary classes:
They are the interface between outside the system. Boundary classes are having objects, which
are changes in the surroundings. That changes affecting system sometimes by user requirements.
Every system has different types of boundary classes, such as user interface, system interface,
and device interface classes (Larman, 2012).
For finding user interface classes, take actors form use cases, each actor has at least one
boundary object. Using object classes coordinate with the actor. The boundary object handles all
responsibilities; sometimes it reduces some responsibilities to the subsidiary objects. Therefore,
each actor should require a boundary object. We can make sketches or take screenshots from
GUI application for creating classes. It is showing flow of events of the use case diagrams
(Liang, 2003).
For system interface classes, external systems are responsible. As an example, In an Automated
Teller Machine (referred as ATM), always check the balance in the customer account. An object
of control class is called for checking the correct information, and according to that takes a
suitable decision. For device interface classes, there are some objects, which are affecting system
working are considered in the device interface classes (Tsang, et al., 2004).
Find Entity Classes
These are present the storage of information in the system. These objects are persistent, and
passive. It is used in the business modeling work for accessing thousands of data chucks in the
information system. Attributes of different entities are also considered in identifying the classes
for better understanding of control flow and data flow in the project.

System Design and Analysis 4
Entity classes are having data. It is related to the data-oriented approach. It is having high
cohesion, which is not easily changed. It added in the class diagram as an entity. Entity classes
are based on the data of the project as in ER-diagrams. All entities are access using the object.
Entity is makes with the help of differed attributes.
Find Control Classes:
These classes are providing coordination between system and behavior controls. It used use case
diagram. Sometimes control classes identify using boundary and entity objects. Use case
diagrams are also a presentation of control flow. It is like de-coupling of use case in a class’s
format. They are providing different things, which are:
 Controls are fix and cannot change by the surroundings
 Each transaction is listed and follow the define control logic
 There should be some Changes according to the need of the system
 All the sets of entity classes can be used for the coordinating other classes
 Flow of control should be maintained every time
There are few steps for finding control classes, which are:
 Finding Control Class from use cases
 Encapsulate Flow of Events and separate Control Classes from others
 Separates control class in the different parts according to actors.
For identifying classes from use case, it is must to understand the use case in different ways,
such as controls flow, information flow, and actors of the system. All these classes are making
complete system. Control classes are so important for designing the system. As other classes can
be, find using the de-coupling of the use case diagram (Van Lamsweerde, 2009). Use case
diagrams are designed according to particular work of an actor in that project. Therefore, it can
be de-coupled and changes it into the classes, but boundaries should be considered for the data
flow and information storage. There are so many things are useful for object-oriented approach,
such as abstraction, and encapsulation of data. Use cases, actors and relationship between both
are used for identification of classes.

System Design and Analysis 5
Conclusion
It is concluded from previous part of this report that, object oriented approaches are the best way
to understanding requirements of a project. It is useful for the cost saving and avoid unnecessary
delays in the project. In this report, different ways of identifying classes was discussed and
which types of classes can created by the help of use-case diagram.
A unified modeling language is an innovation in the field of analyzing requirements of the
systems using different diagram. Use case diagrams are most suitable type of diagrams for
showing flow of control and information. UML provides a better way to understand system
requirements.
Finally, on basis of behavior, identification of classes is simple and best way. It provides
different classes and their objects for managing data and control in the system. The goals of use
cases are helpful for identification of classes.

System Design and Analysis 6
References
Bruegge, B. a. D. A., 2008. Object-Oriented Software Engineering Using UML, Patterns and
Java-(Required) (Vol. 2004).. 4 ed. London: Prentice Hall..
Conallen, J., 2012. Building Web applications with UML.. 6 ed. New York: Addison-Wesley
Longman Publishing Co., Inc...
Gomaa, H., 2011. Software modeling and design: UML, use cases, patterns, and software
architectures.. 2 ed. New York: Cambridge University Press..
Jacobson, . I., 1993. Object-oriented software engineering: a use case driven approach.. 2 ed.
New Delhi: Pearson Education India.
Larman, C., 2012. Applying UML and patterns: an introduction to object oriented analysis and
design and interative development.. 5 ed. New York: Pearson Education.
Liang, Y., 2003. Liang, Y. (2003). From use cases to classes: a way of building object model
with UML. Information and Software technology, 45(2), pp. 83-93.
Tsang, . C. H., Leung, Y. . K. & Lau, C. S., 2004. Object-Oriented Technology. New York:
McGraw-Hill.
Van Lamsweerde, A., 2009. Requirements engineering: From system goals to UML models to
software (Vol. 10).. 2 ed. Chichester: John Wiley & Sons..