1 / 22

Software development process

Software development process. ธนวัฒน์ แซ่เอียบ. The development process. Process set of rules which define how a development project. Methodology and method specify techniques for developing particular design artifacts. It also tells you something about how you should produce these things.

timon-mcmahon
Download Presentation

Software development process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software development process ธนวัฒน์ แซ่เอียบ

  2. The development process • Process • set of rules which define how a development project. • Methodology and method • specify techniques for developing particular design artifacts. • It also tells you something about how you should produce these things. • specifies what modeling language should be used in describing the analysis and design work. • UML is not methodology, but Unified Process is.

  3. process

  4. method • Flowchart • The first major software method. • Structured analysis • organize computer programs into a functionally. • Object oriented • organize computer programs into larger abstractions called objects that mirrored the real world. • Agile methods • improve customer satisfaction.

  5. Methodology • New methodology • Agile Manifesto • XP (Extreme Programming) • Scrum • Crystal • Context Driven Testing • Lean Development • (Rational) Unified Process • unify software processes (like the UML) • same time as the agile methods

  6. Unified process • Unified process (UP) is The development process • UML is the virtual language.

  7. History of UP • RUP is commercial version of UP from IBM

  8. UP phase • Inception • Get the project off the ground. • Elaboration • Create an executable architectural baseline. • Risk assessment. • Define quality attributes. • Construction • Complete all. • Transition • Deploy.

  9. UP phase

  10. UP • defines the who, what, when, and how • Who • Roles. • User particapate in system. • what • activities and artifacts. • Activities are tasks that will be permormed by user. • Artifacts are thing that are input and output. • Source code, programs,standards, documentation • When • Workflow • Sequences of related activities that are preformed by user.

  11. The development process • Any development process aims to produce program • single diagram could capture verything about our design? • So We will build different models of our design, reflecting these different aspectsand will express each model

  12. Models and modeling languages • A model • is an abstract representation of a specification, a design or a system, from a particular point of view. • A modeling language • is a way of expressing the various models produced during the development process.

  13. distinguish models • The use case model • describes the required system from the users’ points of view. • A static model • describes the elements of the system and their relationships. • A dynamic model • describes the behavior of the system over time.

  14. What is the UML? • The Unified Modeling Language is a visual language for specifying, constructing and documenting the artifacts of systems. • Visual is pictures (with some text) related to software primarily OO software. • focuses on frequently used diagrams.

  15. UML 1 and UML 2 • Grady Booch, Ivar Jacobson, and Jim Rumbaugh as its creators . • official Diagram Types of the UML

  16. UML 1 and UML 2 • official Diagram Types of the UML

  17. Classification of UML diagram types

  18. Three Ways to Apply UML • UML as sketch • Informal and incomplete diagrams created to explore difficult parts of the problem or solution space. • often hand sketched on whiteboards. • UML as blueprint • 1) reverse engineering to visualize and better understanding existing code in UML diagrams • 2) code generation (forward engineering). • UML as programming language • Complete executable specification of a software system in UML

  19. Three Perspectives to Apply UML • 1. Conceptual perspective • describing things in a situation of the real world or domain of interest. • 2. Specification (software) perspective • describe software abstractions or components. • 3. Implementation (software) perspective • describe software implementations.

  20. Different perspectives with UML.

  21. Why a unified modeling language? • 1. expressive enough • 2. easy enough to use • 3. unambiguous • 4. supported by suitable tools, so that developers • 5. widely used

  22. ที่มา • UML2 and Unified Process: jim arlow

More Related