Download
1 / 23
230 likes | 242 Views
This methodology emphasizes the importance of Object-Oriented Analysis (OOA) in software development through a structured process, including identifying actors, developing use cases, preparing interaction diagrams, and classifying attributes and methods. It also guides in developing effective documentation using common covers and vocabularies, and identifying classes, relationships, attributes, and methods for efficient system design.
E N D
Unified Approach for a Better understanding of OO Concepts and System Development By M.S.Thanabal, Associate Professor, Department of Computer Science and Engineering, PSNACET.
System Development • Object Oriented System Development • Software Development Methodology • Why we go for Object Orientation • UA – Methodology for software Development
The Object-Oriented Analysis (OOA) Process The process consists of the following steps: 1. Identify the actors: i. Who is using the system? ii. Or, in the case of a new system, who will be using the system? 2. Develop a simple business process model using UML activity diagram. 3. Develop the use case: a. What the users are doing with the system? b. Or, in the case of a new system, what users will be doing with the system? Use cases provide us with comprehensive documentation of the system under study.
4. Prepare interaction diagrams: • Determine the sequence. • Develop collaboration diagrams 5. Classification—develop a static UML class diagram: • Identify classes. • Identify relationships. • Identify attributes. • Identify methods. 6. Iterate and refine: If needed, repeat the preceding steps.
Developing Effective Documentation • Common cover • 80-20 rule • Familiar vocabulary • Make the document as short as possible • Organize the document
I. Identify Classes 1.Noun Phrase Approach 2.Common Class Pattern Approach II. Identify Relationships 1.Association 2.Super – Sub Structure 3.Aggregation and a part of Structure III. Identify Attributes 1.Corresponds to the nouns followed by propositional phrases 2.Omit derived attributes IV. Identify Methods
I.Noun Phrase Approach Initial List of Noun Phrases: Candidate Classes Account, Account Balance, Amount, Approval Process, ATM Card, ATM Machine, Bank, Bank Client, Envelope, Four Digits Eliminate the irrelevant classes Account, Client’s Account, Account Balance, Amount, Approval Process, ATM Card, ATM Machine, Bank, Bank Client Reviewing the Redundant Classes and Building a Common Vocabulary Savings, Savings Account = Savings Account Account, Client’s Account = Account Reviewing the Classes Containing Adjectives Different use of the same object Reviewing the Possible Attributes Was only as values should be defined For e.g. Amount- A value, not a class Reviewing the Class Purpose ATM Machine, ATM Card, BankClient, Bank
