InvoiceNumber : Numeric Here, an attribute named InvoiceNumber contains a numeric value.
1. InvoiceNumber : Numeric Here, an attribute named InvoiceNumber contains a numeric value.
2. Temperature : Numeric { 4 decimal precisions } Here, an attribute name Temperature contains a numeric value with a format of four decimal precisions. 3. SequenceNumber : Integer = 0 {assigned sequentially by the system} Here, an attribute name SequenceNumber contains an integer with a default value of 0. Later on, it will be assigned a number sequentially assigned by the system. To help in discovering and specifying attributes, one can use the guideline below. 1. Sources of possible attributes are system domain knowledge, requirements and glossary. 2. Attributes are used instead of classes when: • Only the value of the information, not its location, is important. • The information is uniquely owned by the object to which it belongs; no other objects refer to the information. • The information is accessed by operations which only get, set or perform simple transformations on the information; the information has no real behavior other than providing its value. 3. If the information has complex behavior, or is shared by two or more objects the information should be modeled as a separate class. 4. Attributes are domain dependent. 5. Attributes should support at least one use case. Software Engineering 104 J.E.D.I In our example, the following attributes identified are shown in Figure 3.28. Similar to the previous step, all attributes seen in the collaboration diagrams should be compiled into a single analysis class. As an example, the :Athlete analysis class has the following attributes: id, lastname, firstname, mi, address, postalCode, telephone, bday, gender, and status. Software Engineering 105 Figure 3.28 Attribute Identification J.E.D.I Step 6: For each resulting analysis classes, identify associations. An association represents the structural relationships between objects of different classes. It connects instances of two or more classes together for some duration. It may be: 1. Unary Association which is a relationship of objects of the same class. 2. Binary association which is a relationship of two objects of different classes.3. Ternary association which is a relationship of three or more objects of
Parts
» | Komputasi | Suatu Permulaan
» Quality Focus Process Method Tools
» What is quality? How do we define quality?
» Software Quality Characteristics of a Well-engineered Software
» Software Quality Assurance Activities Formal Technical Reviews
» Types of Software Process Models
» Understanding Systems | Komputasi | Suatu Permulaan
» End-users Understanding People in the Development Effort
» What is documentation? Criteria for Measuring Usability of Documents
» Abstraction Encapsulation Review of Object-oriented Concepts
» Modularity Hierarchy Review of Object-oriented Concepts
» Project Assignment Object-oriented Process Model
» Modeling Activity Unified Modeling Language UML
» UML Baseline Diagrams Unified Modeling Language UML
» Requirements Engineering Concepts | Komputasi | Suatu Permulaan
» Inception Requirements Engineering Tasks
» Elaboration Negotiation Requirements Engineering Tasks
» Specification Validation Requirements Engineering Tasks
» Management Requirements Engineering Tasks
» Scenario Modeling Requirements Analysis and Model
» Requirements Model Validation Checklist
» InvoiceNumber : Numeric Here, an attribute named InvoiceNumber contains a numeric value.
» Ternary association which is a relationship of three or more objects of
» The Analysis Model Analysis Model Validation Checklist
» Requirements Traceability Matrix RTM
» Requirements Metrics | Komputasi | Suatu Permulaan
» The Design Model Design Engineering Concepts
» Describing the Package Diagram Developing the Architectural Design
» Software Architecture Validation Checklist
» Developing the Data Design Model
» Report Design Interface Design
» Forms Design Interface Design
» Basic Component Design Principles Component-level Design Guidelines
» Component Diagram Developing the Software Component
» Project Assignment Design Model Validation Checklist
» Mapping the Design Deliverables to the Requirements Traceability Matrix Design Metrics
» Creating the Data Design Model Creating the Interface Design Creating the Control Design
» Project Assignment Programming Standards and Procedures
» Using Pseudocodes Control Structure Guidelines Documentation Guidelines
» Implementing Packages | Komputasi | Suatu Permulaan
» Abstract Classes Implementing Controllers
» Interfaces Why do we use Interfaces?
» Interface vs. Abstract Class Interface vs. Class Creating Interfaces
» Relationship of an Interface to a Class Inheritance among Interfaces
» Implementing Java Database Connectivity JDBC
» AWT GUI Components Implementing the Graphical User Interface
» Layout Managers Implementing the Graphical User Interface
» Controlling the Version of the Software
» Introduction to Software Testing
» White-Box Testing Techniques Software Test Case Design Methods
» Black-Box Testing Techniques Software Test Case Design Methods
» Testing your Programs | Komputasi | Suatu Permulaan
» Test-driven Development Steps Test-driven Development Methodology
» Testing Java Classes with JUnit
» Testing the System | Komputasi | Suatu Permulaan
» Mapping the Software Testing Deliverable to the RTM Test Metrics
» Project Assignment Software Project Management
» Problem Identification and Definition
» The Project Team Structure Project Responsibility Chart
» Project Work Breakdown Structure WBS
» Work Breakdown Schedule Format
» Size-oriented Metrics- Lines of Codes LOC Function-Oriented Metrics: Function Points FP
» Project Estimations | Komputasi | Suatu Permulaan
» The Risk Table Risk Management
» Risk Identification Checklist Risk Management
» Baseline Software Configuration Tasks
» Writing the Project Plan Project Assignment Case Tools
Show more