{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

all slides software engineering

all slides software engineering - CEN 4010 Software...

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

View Full Document Right Arrow Icon
CEN 4010 Software Engineering 1 Instructor: Frank Hernandez https://www.cs.fiu.edu/~fhern006 Spring 2011 Adapted from Dr. Clarke’s slides.
Background image of page 1

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

View Full Document Right Arrow Icon
2 Course Introduction Syllabus Project Questions What is s/w eng.?
Background image of page 2
3 Overview of Software Process Definition. Why S/w Eng.?
Background image of page 3

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

View Full Document Right Arrow Icon
4 What is Software Engineering? Software Engineering is the application of a  systematic, disciplined, quantifiable approach to the  development, operation and maintenance of software;  that is, the application of engineering to software. (5/5 points) (Source: IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology)
Background image of page 4
5 What is Software Engineering? cont “Software engineering is an engineering discipline which is concerned with all aspects of software production.” Sommerville (3/5points) Software engineering is modeling problem-solving knowledge acquisition rationale-driven (3/5 points) Bruegge & Dutoit
Background image of page 5

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

View Full Document Right Arrow Icon
6 Modeling “A model is an abstract representation of a system that enables us to answer questions about the system.” Why use a model? Systems are too large, too small, too complicated, or too expensive, to experience firsthand. Models allow visualization comprehension
Background image of page 6
7 Problem Solving Steps in problem solving: 1. formulate the problem 2. analyze the problem 3. search for solutions 4. decide on the appropriate solution 5. specify the solution
Background image of page 7

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

View Full Document Right Arrow Icon
8 Knowledge Acquisition Domain specific knowledge. New knowledge can affect the development process. Knowledge acquisition is nonlinear – affects several of the software development models. Risk assessment is important.
Background image of page 8
9 Rationale Management Assumptions made about systems change constantly. Application domain models stabilize, solution domain models are in constant flux. e.g. Changes to the solution models due to: design and implementation faults new technology Need to understand the context in which each design decision was made.
Background image of page 9

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

View Full Document Right Arrow Icon
10 Important Terms participants  – all persons involved in a project. e.g., developers, project manager, client, end users. role – associated with a set of tasks assigned to a participant. system – underlying reality. model – abstraction of the reality. work product – an artifact produced during development. deliverable – work product for client.
Background image of page 10
11 Important Terms cont activity – a set of tasks performed toward a specific purpose. milestone – end-point of a software process activity. task – an atomic unit of work that can be managed and that consumes resources. goal – high-level principle used to guide the project. functional requirement – an area of functionality that the system must have.
Background image of page 11

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

View Full Document Right Arrow Icon
12 Important Terms cont nonfunctional requirement – a constraint on the system.
Background image of page 12
Image of page 13
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}