MCS morning (3rd semester) Department of CS&IT

Designing objects

Topics: Agile modeling Lightweight UML Uml case tools Time spent on drawing before coding Dynamic and static Modeling Presented by: Hira shafi Faehah Hassan

Agile Modeling: Agile modelling (AM) is a methodology for modelling and documenting software systems based on best practices. It is a collection of values and principles, that can be applied on software development project.  Agile model is a combination of iterative and incremental models with focus on process adaptability and customer satisfaction by rapid delivery of working software product. Agile methods break the product into small incremental builds. These builds are provided in iterations.

Advantages: very realistic approach to software Promotes teamwork Resource requirements are minimum. Suitable for fixed or changing requirements Delivers early partial working solutions Good model for environments that change steadily. Easy to manage

Disadvantages: Difficult to apply where No fixed pricing There are large team Team members are not co-located People skills are lacking No fixed pricing Training the client Not suitable for complex software Depends heavily on customer interaction, so if customer is not clear, team can be driven in the wrong direction.

Lightweight UML Agile modeling emphasizes UML as sketch Some aims of agile modeling are to reduce drawing overload. Try using simple practices whiteboards markers digital cameras

Uml Case tools:

Choosing uml case tools:

Some uml case tools: StarUML (open-source) Umbrello (open-source) AgroUML (open-source) Microsoft Visio (commercial) Visual paradigm GenMyModel (online) Creately (online)

How Much Time is Spent in Drawing UML Before Coding ??

For a three-week time boxed iteration, spend a few hours or at most one day (with partners) near the start of the iteration "at the walls" (or with a UML CASE tool) Then stop - and if sketching - perhaps take digital photos, print the pictures, and transition to coding for the remainder of the iteration Using the UML drawings for inspiration as a starting point, but recognizing that the final design in code will diverge and improve. Shorter drawing/sketching sessions may occur throughout the iteration.

Static and dynamic Modeling

STATIC MODELING Class diagram Object diagram Static modeling: Static Modeling is used to represent the static constituents of a Software such as : 1.Classes, 2.Objects, 3.Interfaces and 4.Their relationship with each other. STATIC MODELING Class diagram Object diagram

DYNAMIC MODELING to represent the behavior of the static constituents of a software , here static constituents includes, classes , objects, their relationships and interfaces to represents the interaction, workflow, and different states of the static constituents in a software.

Collaboration diagram Dynamic Modeling Dynamic Modeling Activity Diagram Interaction Diagram Sequence diagram Collaboration diagram

Class Diagram (static)

Sequence diagram (dynamic)

Thankyou!  House is open for Queries ;)