Software Development Process Aditya P Mathur Purdue University

Software Development Process Aditya P. Mathur Purdue University Analysis: June 7 -8, 1999 Design: June 9 -11, 1999 @ Raytheon Technical Services, Indianapolis. Graduate Assistants: Last update: June 6, 1999 Design Part I June 9 -11, 1999 Software Design Sudipto Ghosh Matt Baarman

Topics to be covered z Review: Actors and use cases z Development process z Design y. Basic principles y. Collaboration diagrams y. Principles and guidelines (again) y. Class diagrams y. Deployment diagrams June 9 -11, 1999 Software Design 2

Actors (1) z. Who is an actor? y. An entity “external” to the system. y. This entity participates in some way in at leas one domain process. y. This entity typically stimulates the system with input events or receives something from it. June 9 -11, 1999 Software Design 3

Actors (2) z. Initiator Actor: y. One who initiates a domain process. z. Participating actor: y. One who participates in a domain process. z. Actors are usually: y. Humans playing a role ycomputer systems yelectrical or mechanical devices…anything remains ? June 9 -11, 1999 Software Design 4

Actors (3) z. How to choose an actor? y. Identify a least one user who can enact an actor. y. Maintain a minimum overlap between the roles that instances of different actors play in relation to the system. Avoid two or more actors having the same or similar roles. June 9 -11, 1999 Software Design 5

Use cases z. What is a use case? y. A domain process. y. We give it a name. y. We identify an actor that initiates this domain process and gets value out of this domain process. June 9 -11, 1999 Software Design 6

Discussion z. Is the internet an actor ? y. Compare the internet with the communication system used by POST to send logging information to a central computer in the store. z. Is a weapon an actor ? y. Compare the weapon with the Point of Sale Terminal (the actual cash register). y. Compare a commander-weapon pair with a buyerseller pair. Any differences? Similarities? June 9 -11, 1999 Software Design 7

A development process (1) z Phases z Workflows z Iterations June 9 -11, 1999 Software Design 8

A development process (2) z Phases y. Inception y. Elaboration y. Construction y. Transition June 9 -11, 1999 Software Design 9

A development process (3) z Workflows y. Requirements y. Analysis y. Design y. Implementation y. Test June 9 -11, 1999 Software Design 10

A development process (4) z Iterations: y. Each phase might go through one or more iterations. z Examples: y. Requirements might go through two iterations during the inception phase. y. In the elaboration phase one might go through two iterations of R, A, D, I, and T. June 9 -11, 1999 Software Design 11

Workflows-Phases Workflows Inception Elaboration Construction Transition R A D I T Iter# 1 June 9 -11, 1999 Iter# 2. . . Iterations Software Design 12