DOC PREVIEW
WVU CS 430 - Practice

This preview shows page 1-2 out of 6 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 6 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 6 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 6 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20051WVU, LCSEEWVU, LCSEECS 430CS 430Fall 2004Fall 2004copyright © 1996, 2001, 2005R.S. Pressman & Associates, Inc.For University Use OnlyMay be reproduced ONLY for student use at the university levelwhen used in conjunction with Software Engineering: A Practitioner's Approach.Any other reproduction or use is expressly prohibited.These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20052What is What is ““PracticePractice””??Practice is a broad array of concepts, principles, Practice is a broad array of concepts, principles, methods, and toolsmethods, and toolsthat you must consider as software is that you must consider as software is planned and developed.planned and developed.It represents the detailsIt represents the details——the technical considerations the technical considerations and howand howtoto’’ss——that are below the surface of the software that are below the surface of the software processprocess——the things that youthe things that you’’ll need to actually build ll need to actually build highhigh--quality computer software.quality computer software.These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20053The Essence of PracticeThe Essence of PracticeGeorge George PolyaPolya, in a book written in 1945 (!), describes the , in a book written in 1945 (!), describes the essence of software engineering practice essence of software engineering practice ……Understand the problemUnderstand the problem(communication and analysis).(communication and analysis).Who are stakeholders? What are unknowns (data, featuresWho are stakeholders? What are unknowns (data, features……)?)?Plan a solutionPlan a solution(modeling and software design).(modeling and software design).Has a similar problem been solved? Can Has a similar problem been solved? Can subproblems subproblems be defined?be defined?Carry out the planCarry out the plan(code generation).(code generation).Does the solution confirm to the plan? Is each component correctDoes the solution confirm to the plan? Is each component correct??Examine the result for accuracyExamine the result for accuracy(testing and quality assurance).(testing and quality assurance).Can components be tested? Do solutions conform with expectationsCan components be tested? Do solutions conform with expectations??At its core, good practice is At its core, good practice is commoncommon--sense problem sense problem solvingsolvingThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20054Core Software Engineering Core Software Engineering PrinciplesPrinciplesProvide value to the customer and the userProvide value to the customer and the userIs this valuable to potential users?Is this valuable to potential users?KIS(S)KIS(S)——keep it simple (stupid)!keep it simple (stupid)!Maintain the product and project Maintain the product and project ““visionvision””No patchwork design.No patchwork design.What you produce, others will consumeWhat you produce, others will consumeBe open to the futureBe open to the futurePlan ahead for reusePlan ahead for reuseThink!Think!These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20055Software Engineering Software Engineering PracticesPracticesConsider the generic process frameworkConsider the generic process frameworkCommunicationCommunicationPlanningPlanningModelingModelingConstructionConstructionDeploymentDeploymentHere, weHere, we’’ll identifyll identifyUnderlying principlesUnderlying principlesHow to initiate the practiceHow to initiate the practiceAn abbreviated task setAn abbreviated task setThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20056Communication PracticesCommunication PracticesPrinciplesPrinciplesListenListenPrepare before you communicatePrepare before you communicateFacilitate the communicationFacilitate the communicationFaceFace--toto--face is bestface is bestTake notes and document decisionsTake notes and document decisionsCollaborate with the customerCollaborate with the customerStay focusedStay focusedDraw pictures when things are unclearDraw pictures when things are unclearMove on Move on ……If you agree, disagree, clear or unclearIf you agree, disagree, clear or unclearNegotiation works best when both parties win.Negotiation works best when both parties win.These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20057Communication PracticesCommunication PracticesInitiationInitiationThe parties should be physically close to one anotherThe parties should be physically close to one anotherMake sure communication is interactiveMake sure communication is interactiveCreate solid team Create solid team ““ecosystemsecosystems””Use the right team structureUse the right team structureAn abbreviated task setAn abbreviated task setIdentify who it is you need to speak withIdentify who it is you need to speak withDefine the best mechanism for communicationDefine the best mechanism for communicationEstablish overall goals and objectives and define the scopeEstablish overall goals and objectives and define


View Full Document

WVU CS 430 - Practice

Documents in this Course
Lecture

Lecture

28 pages

Design

Design

27 pages

Load more
Download Practice
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Practice and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Practice 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?