Escolar Documentos
Profissional Documentos
Cultura Documentos
ANALYSIS MODEL
SUBMITTED BY: AMAN GUPTA ABHISHEK KUMAR C.SRIKAR DEEPAK KUMAR SONI 100101025 100101009 100101071 100101074
Acknowledgement
I am also grateful to my project supervisor Mrs. RITIKA CHUGH
who without his/her help and guidance this project would not have been completed.
I also show my gratitude to my friends and all who contributed in one way or the other in the course of the project
I wish to thank my parents for their tremendous contributions and support both morally and financially towards the completion of this project
Table of Contents
S. No.
1. 2. 3. 5. 6. 7. 8. Content Acknowledgement Objectives The analysis model Goals of analysis model Aims of Analysis Model Types of Object Producing an Analysis Model
Approaches Elements of the Analysis Model Inputs & Outputs Analysis Notations
13
References
Objectives
This Unit will outline the construction of the Analysis ModelBuildingon outputs of Requirements Model. It will describe the basic UML notations associated with analysis and introducenew types of analysis objects . The use cases will be used andrefined and the inputs for Design Model defined..
Deals with the problem of size by partitioning the system Uses graphics whenever possible Differentiates between essential implementation information information versus
Helps in the tracking and evaluation of interfaces Provides tools other than narrative text to describe software logic and policy
Types of Object
Interface
or interface objects "One distinguished role is that of the controller. The controller receives the request to invoke the system operation. The system operation is part of the method interface of the controller." The controller is "responsible for responding to a system operation request." "A design should have interface objects for each related set of operations at the subsystem interface."
Objects-Controller
All functionality specified in the use case description that is directly dependent on the system environment is placed in interface objects. Actors communicate with the system through these objects. The task is to translate the actors input to the system into events in the system, and to translate these events into something which is presented to the actor
EX-
model functionality thatis not naturally tied to any other object. Typically such behaviour ...consists of operating on several different entity objects, doing some computationsand then returning the result to an interface object." Used to model behavior that is not naturally placed in either of another two objects (interface and entity)Typical type of functionality placed in the control objects aretransaction-related behavior, orcontrol sequences specific to one or a few use cases, orfunctionality that separates the entity objects from the interface objects.
Ex-
Subsystem:
include other subsystems." "The task of subsystems is topackage the objects so that the complexity is reduced." "Theaim is to have a strong functional coupling within a subsystem and a weakcoupling between subsystems." Ex-
Draft initial class diagram Re-examine behaviour ii n use cases and objects Refine class diagram Execute check Revise class diagram Group classes into packages
Object-oriented analysis
Focuses on the definition of classes and the manner in which they collaborate with one another to fulfill customer requirements
class roles and responsibilities [Text] use case description in terms of classes and operations
Analysis Notations Notations introduced:: class (rectangle containing name,, attributes,, operations) object (rectangle plus obx:Cx) association (by value/aggregation,, cardinality/multiplicity) generalisation (UML term replacing OOSE inheritance) package depends association
REFERENCES:
http://en.wikipedia.org/wiki/File:Analysis_Model_Objects.jpg http://www.rspa.com/spi/analysismodeling.html http://en.wikipedia.org/wiki/Structured_analysis