Discuss topic show exercise solution and discuss to more practircal

exam question: topic 1 and topic 2

what is model an show some concreate model
explain syntax semantic

1. why system development: follow recipe follow certain steps(when cook a turkey for example).
Expereinced team: still follow the methology, feel and do what you want. Employer want to have
deadline need to findout bring more p.p in project to be able to catch up. Emplyer know what goal
and what time. Aline something work together.
2. iterative method: sprial model. Repeat increament product, from scratch. Look at requirement
anytime. Do no. Of step building a bit of final software at a time. (when get tested build it as final of
product(exe base line) you still have product even though 1 interation not approved still have some
functionality( to adjust it according to customer get early feedback and you can adjust. Can addapt
to changeable to change to course of project),
prob w/ water fall(requirements)-(design) implement(2yrs)- what if you arwrong so no adapt, pr
3.agile: adjust, flesible, iterative, hard to adpat w/ waterfall,(strict in timebox)functionality, ab not
making model, light weight dont make these models on fornt(misunderstood): make UML: do it
whenever you need it, more adapt, unclear how to implement that(sketch on white board) until
group find a design, will not type them in and refactingnot making models. Many flavor: agile UP,
strict. (scrum is scrum but agile)
4: model : model when u need to design : foward as design, at end of documentation(reverse)
5. dif btw diagram and model: size: diagram larger(dynamics, class diagram): presentation of
info just another way of presenting(description of to be) model has purpose consist of 1 or more
diagram(ER model model of conceptual data) diagram(class diagram) to make model usecase
model consist diagram usecase model consist 5 dif artifact. Model larger than diagram bcs
model consist more diagram( look at dynamics and static) business model
why use this digram: when show some diagram.
6.Traceability: trace the code from models, no need to read complicated code. Traceability btw all
the models.
7. Types of models: Statics: class diagram, domain model
Dynamics: Use case diagram, use case text description( sale), SD, SSD
II:
For UP
The requirements are unknown or hard to elicit from the user
The requirements change frequently
Embracing Change
Each iteration involves choosing a small subset of the requirements and quickly design, implement

and testing them

This leads to rapid feedback, and an opportunity to modify or adapt understanding of the
requirements or design
23
A requirement describes
a condition or capability
to which a system must
conform; either derived
directly from user needs,
or stated in a contract,
standard, specification,
or other formally

imposed document.
For UML:

3. Use case: Use cases capture the functional requirements of a system.

Use cases describe the interactions between actors and the system from the users
perspective
Use cases must have business value
Use cases divide the system into meaningful parts meaningful parts not just a list of
functions
Use cases describe how goals are achieved through use of the system I.e. the work
process when the system is build
Use case scenario:

Concepts related to use cases

Actor: something with behaviour, and having a goal using the system, such as a person,
computer system, or organization, e.g. a cashier.
Goal: What the actor wants to achieve by interacting with the system.
Scenario: specific sequence of actions and interactions between actors and the system
under discussion, e.g. the scenario of successfully purchasing items with cash. An instance
Use case: a collection of related success and failure scenarios that describe actors using a
system to support a goal.

4. Conceptual models:
Domain Model (conceptual model - class diagram)

III: Design.
GRASP Patterns
2 goals (what we want) High
Cohesion Low Coupling
3 means (how we get it)
Information Expert Controller
Creator