chapter12 - Objectives Learn how software engineering is...

Info iconThis preview shows pages 1–12. Sign up to view the full content.

View Full Document Right Arrow Icon
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Objectives Learn how software engineering is used to create applications Learn some of the different software engineering process models Understand what a design document is and how it should be used during software development Be introduced to the proper steps in formulating a design document used in creating an application
Background image of page 2
Objectives (continued) Learn how Unified Modeling Language (UML) diagrams can be used as a blueprint in creating an application See some of the pitfalls in developing software, and learn how to avoid them Gain an understanding of how teams are used in application development
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
What is Software Engineering? The process of producing software applications Source code UML diagrams and screen prototypes Requirements and reports Future development issues The end user is the driving force behind software development Determines the required functionality of the program
Background image of page 4
Software Development Life Cycle Describes the life of the application including the development, testing, installation, and maintenance of the program Elements of the SDLC Project feasibility Software specification Software design and implementation Software validation Software evolution
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Software Development Life Cycle (continued) Models of the software development process Waterfall The output from each development phase is used as the input to the next phase Build and fix The developer writes a program and continues to modify it until the system is functional Rapid prototyping Tools allow end users to work with user interface prototypes before building the final product
Background image of page 6
Software Development Life Cycle (continued) Incremental Development with a series of software releases Spiral Cycles through the waterfall approach until all functionality has been completed Extreme programming (XP) Places emphasis on teamwork and feedback
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Figure 12-1 The “waterfall” model of software development
Background image of page 8
Creating the Design Document A design document details all of the design issues for an application Issues include screen layouts, colors, reports, security, paths for files, online help, user documentation, future plans, and more Acts like a blueprint for the system Based upon good communication with the end user in determining requirements
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Figure 12-2 Process of creating a design document
Background image of page 10
Step 1: Learn the Current System and Needs Case Study: a media inventory for a music store
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 12
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/08/2012 for the course SADSAD sdsadasdas taught by Professor Dasda during the Spring '11 term at Alaska Bible.

Page1 / 40

chapter12 - Objectives Learn how software engineering is...

This preview shows document pages 1 - 12. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online