Programming Engineering of Standalone Programs

Software engineering of standalone programs l.jpg
1 / 43
0
0
455 days ago, 279 views
PowerPoint PPT Presentation
Programming Designing of Standalone Projects. Prof. Ruth Dameron, dameron@colorado.edu Course site with course materials is under WebCT Need an identikey and secret word Call 303-735-HELP. Course site substance. Go to http://webct.colorado.edu/

Presentation Transcript

Slide 1

´╗┐Programming Engineering of Standalone Programs Prof. Ruth Dameron, dameron@colorado.edu Course site with course materials is under WebCT Need an identikey and secret word Call 303-735-HELP

Slide 2

Course site substance Go to http://webct.colorado.edu/Login in the event that you have identikey and client watchword Lecture material - PowerPoint documents Print in "freebee" or in Notes organize "Immaculate highly contrasting" Homework assignments Some extra things, for example, short articles or book extracts Other course data syllabus with perusing assignments, occasions reading material data, PowerPoint address records last test of the year data available time, contact data

Slide 3

Part of an entire Software Engineering Certificate - 9 hrs graduate credit http://ece.colorado.edu/~swengctf/Software Engineering of Standalone Programs Software Engineering of Multiprogram Systems Software Engineering of Distributed Systems The connections at the above site indicate course materials that are not under control of WebCT. Their motivation is to give you a chance to perceive what is shrouded in the 3 courses Warning: Lecture takes note of that match the ones I use in class PLUS your homework assignments are the ones that are under WebCT.

Slide 4

Requirements Engineering Slides initially created by Michael Madigan StorageTek Manager, PAL Engineering

Slide 5

Cobb's Paradox "We know why ventures fall flat, we know how to keep their disappointment - so why do regardless they fizzle?" Martin Cobb Treasury Board of Canada Secretariat Ottawa, Canada

Slide 6

Project Resolution Type 2 Challenged Resolution Type 1 Project Success Resolution Type 3 Impaired

Slide 7

Cost Overruns Percent Over Budget

Slide 8

Time Overruns Percent of Time Under Estimated

Slide 9

Content Deficiencies Percent of Originally Planned Functionality

Slide 10

Project Success Factors Other User Involvement Ownership Executive Management Support Smaller Project Milestones Realistic Expectation Competent Staff Clear Statement of Requirements Proper Planning Clear Vision and Objectives Hard-Working Focused Staff

Slide 11

Top Ten Project Success Factors 1. client association 2. official administration bolster 3. clear articulation of prerequisites 4. appropriate arranging 5. practical desires 6. littler venture developments 7. skilled staff 8. possession 9. clear vision and destinations 10. persevering, centered staff

Slide 12

Properties of Challenged Projects Other Unclear Objectives Lack of User Involvement Inc. Necessities & Specs Changing Requirements & Specs Unrealistic Time Frame Unrealistic Expectation Technology Incompetence Lack of Resources Lack of Executive Support New Technology

Slide 13

Top Ten Challenged Project Factors 1. Absence of client inclusion 2. Inadequate necessities and determinations 3. Changing prerequisites and details 4. Absence of official bolster 5. Innovation Incompetence 6. Absence of Resources 7. Unreasonable desires 8. Indistinct goals 9. Farfetched time period 10. New innovation

Slide 14

Incomplete Requirements Other Didn't Need any Longer Lack of User Involvement Changing Requirements & Specs Lack of Resources Lack of IT Management Technology Illiteracy Unrealistic Expectations Lack of Executive Support Lack of Planning Properties of Impaired Projects

Slide 15

Top Ten Impaired Project Factors 1. Fragmented prerequisites 2. Absence of client inclusion 3. Absence of assets 4. Farfetched Expectations 5. Absence of official bolster 6. Changing prerequisites & specs 7. Absence of arranging 8. Didn't require any longer 9. Absence of IT administration 10. Innovation absence of education

Slide 16

Case Studies

Slide 17

High Level Software Concepts Model Based (System) Architecture Software Engineering (MBASE) Iterative Development (dexterous strategies)

Slide 18

The Model-Clash Spider Web: Master Net 7

Slide 19

Business case IKIWISI Stakeholder win-win Life cycle stay focuses Risk administration Key practices Domain show Requirements Architecture Code Documentation Cost Schedule Performance Reliability MBASE Integration Framework 7 Success models Process Product section/leave assessment criteria Planning and control Process models Product models Milestone content Evaluation and examination Property models

Slide 20

What Does a Process Do for You? A product advancement handle gives you The data you require When you require it In a shape that you can use to such an extent or as meager as you need Easy to discover what you require

Slide 21

Dynamic structure Phases Process Disciplines Inception Elaboration Construction Transition Business Modeling Requirements Analysis & Design Implementation Static structure Test Deployment Configuration Mgmt Proj. Administration Environment Preliminary Iteration(s) Iter. #1 Iter. #2 Iter. #n Iter. #n+1 Iter. #n+2 Iter. #m Iter. #m+1 Iterations Introducing the Rational Unified Process Made Practical

Slide 22

Tools Unified Tools for the Project Team Best Practices Process Made Practical Tools Unified Tools for the Project Team Select and Deploy Best Practices Plan and Execute Iterative Projects Develop Iteratively Manage Requirements Use Component Architectures Model Visually (UML) Continuously Verify Quality Manage Change Requirements Management Visual Modeling Automated Testing Content Management Change Management Plan and Execute Iterative Projects Requirements Management Visual Modeling Automated Testing Content Management Change Management Measure Progress and Quality Measure Progress and Quality Collaborate & Communicate Project Information Collaborate & Communicate Project Information Unified Software Project Management Unified Software Project Management: an incorporated answer for send, arrange, execute, and screen best practices

Slide 23

Requirements Engineering The trained use of logical standards and procedures for creating, conveying, and overseeing prerequisites. 6

Slide 24

User Requirements User Requirements Component Development Systems Requirements Engineering Lifecycle User Requirements Acceptance Test Capability Development System Requirements System Architecture Integration Test System Development Component Development

Slide 25

Software Requirements Architectural plan Integration & Verification Detailed outline & coding User Requirements User Requirements User Requirements Component Development Component Development Lifecycle

Slide 26

Requirements Engineering

Slide 27

Requirements Elicitation Identify applicable wellsprings of necessities (typically client) Determine what data is required. Examine the assembled data, searching for suggestions, irregularities, or uncertain issues Confirm your comprehension of the necessities with the source Synthesize fitting proclamations of the prerequisites Software Requirements

Slide 28

Outcome of good elicitation exercises The purchaser/client completely investigate and completely comprehend their prerequisites. The purchaser/clients can isolate their needs from their requirements. The purchaser/clients can comprehend the abilities and constraints of PC innovation. The purchaser/clients comprehend the option arrangements and effect of every option. The purchaser/clients comprehend the effect of the prerequisites on the engineer and themselves. The engineers are taking care of the correct issue. The designers have certainty that the framework to be conveyed is achievable to assemble. The designers have the trust and certainty of the client. The engineers pick up space learning of the framework

Slide 29

Outcome of poor elicitation exertion The client likely will be disappointed. The client and designer need to adapt to continually evolving necessities. The engineer is taking care of the wrong issue. The designer has a troublesome time fabricating the framework.

Slide 30

Project Success Factors User Involvement Executive Management Support Other Smaller Project Milestones Ownership Clear Statement of Requirements Realistic Expectation Proper Planning Competent Staff Clear Vision and Objectives Hard-Working Focused Staff Requirements Elicitation User Involvement Criteria 2 Do I have the privilege user(s)? Did I include the user(s)early and frequently? Do I have a quality user(s) relationship? Do I make contribution simple? Did I discover what the user(s) needs? Programming Requirements

Slide 31

Requirements Analysis Obtain Requirements from every single conceivable source (incorporate however not restricted to): perception and estimations of the present framework interviews with clients current framework documentation plausibility considers models and models focused investigation Software Requirements

Slide 32

Quality properties

Slide 33

Requirements Specification Software work Performance External Interfaces Design Constraints Quality Attributes Software Requirements

Slide 34

Statement of Requirements Criteria Project Success Factors Do I have a succinct vision? Do I have a useful investigation? Do I have a hazard evaluation? Do I have a business case? Can I gauge the venture? Programming Requirements

Slide 35

Requirements Verification To distinguish and resolve programming issues and high hazard issues right on time in the product cycle. The confirmation that the product prerequisite detail is in consistence with the framework necessities, adjusts to archive benchmarks, and is a sufficient reason for the engineering outline. Joining & Verification

Slide 36

Requirements Management Basic duty is to keep extend inside expenses, inside spending plan, and to address clients issues. Gauge cost of framework in view of necessities. Control the unpredictability of the necessities. Deal with the necessities setup of the framework Negotiate prerequisite changes Re-assess cost of the framework when necessities change. Programming Requiremen

SPONSORS