Sequence Diagram Generation Validation MSE First Presentation Samer

Sequence Diagram Generation & Validation MSE First Presentation Samer Saleh Advisor: Bill Hankley

Introduction n n Software modeling & modern software engineering. Software modeling is not about drawing models only. M. Validation M. Quality S. Quality Model Validation:

Introduction - Continue UML class diagram and sequence diagram are one of the essential models for starting the modeling process. n Class and sequence models are heavily correlated. n Usually this correlation. n

Introduction- Continue n Example 1:

Example 2:

Examples Conclusion Inconsistency between class and sequence diagrams are very common. n Tools are needed to validate & suggest solutions if there any. n

What is done so far…. n n A lot of research has been done to validate model. Yet not much implementation. Formalism of the UML diagrams. Problem: Hard to understand. Difficult to implement by novice software engineers. Problem: Current tools doesn’t check for a lot of validation.

Project idea…. Create/Reload Class Model Create Sequence Model [Not Valid] Generate Error Message. Validate View [Valid] Generate Sequence Model

Project Goals 1. 2. 3. 4. Create a user friendly tool to assist user to generate sequence diagram. Insure reliable and consistent generated sequence diagram. Satisfies the software process and life cycle. Meeting IEEE standards for software documentation

Risks…. n n n Difficulty of using the Java Swings and other java graphical libraries. Difficulty of embedding the validation rules, generating meaningful error messages & suggesting solutions Time concern.

Validation Rules Focused on messages n Only Semantics or Structural. n No Syntax (Implicit). n

Rule #1: Direct/Indirect Association n n Message corresponds to direct or indirect ( transitive ) association. Example:

Rule#2: Dependency Existence For indirect association; at least one path that covers all dependant classes. ?

Rule#3: Reference Existence n For Indirect Association: 1. For all predecessor messages out of the sender object, there is at least one message where the return type is the receiver object. For all predecessor messages in the sender object, there is at least one message where the parameter passed is type of the receiver object. 2.

Rule#3: Example

GUI Prototype- Main Interface Tool Panel Class Model View Pseudo Code View

UI- Creating Class Model

UI – Class Information

UI- Creating Association

UI- Association Information

UI- Creating Sequence Model

UI- Creating Sequence

UI- Viewing the sequence

UI- Analyzer

UI- Analyzer

Schedule First Presentation April 15 th 2 nd Presentation June 20 th Documentation Design. Coding. Testing. Presentation

Schedule- Continue Last Presentation July 21 st Documentation Design. Coding. Testing. Presentation

Cost Estimation Using COCOMO. n SLOC = 116. 4 * 38 = 4423. n Person Productivity (PM) = 11. 4 person-month. n Development Time (TDEV)= 6. 3 months. n Average Staffing = 11. 4/6. 3 = 1. 8 people n

For more information…. http: //www. cis. ksu. edu/~ssaleh/mseproject. htm