DOC PREVIEW
USC CSCI 577 - ec-16b_processes

This preview shows page 1-2-3-4-5 out of 14 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 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 14 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 14 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 14 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 14 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Comparison between each special caseOutlineWhich process should our team follow?Special Case Decision DriverWhat are the differences between each process?Different Risk Patterns Yield Different ProcessesSlide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Should we select the process now?University of Southern CaliforniaCenter for Systems and Software EngineeringComparison between each special caseSupannika Koolmanojwong09/30/09University of Southern CaliforniaCenter for Systems and Software EngineeringOutline•Which process should our team follow?•What are the differences between each process?•Should we select the process now? @USC CSSE 2University of Southern CaliforniaCenter for Systems and Software EngineeringWhich process should our team follow?•Architected Agile–Use some system NDI (MySQL, PHP)–Develop 70% of the functionalities•Use NDI–One product satisfies all solution•NDI-Intensive–Extend from current system (treat current system as predefined module)–Have some COTS, open source that fits more than 30% of solution•Net-Centric Services–Have some services that fit more than 30% of solution@USC CSSE 3University of Southern CaliforniaCenter for Systems and Software EngineeringSpecial Case Decision Driver Importance*Architected Agile Use NDI NDI-Intensive NCS AlternativesMore than 30% of features available in NDI/NCS *** *** *** Has a single NDI/NCS that satisfies a complete solution *** *** Very unique/ inflexible business process *** Life CycleNeed control over upgrade / maintenance *** Rapid Deployment; Faster time to market *** ** ** ArchitectureCritical on compatibility *** *** Internet Connection Independence *** ** ** Need high level of services / performance *** * * * Need high security *** ** ** * Access Data anywhere ** * ** *** ResourcesSchedule constraint *** *** *** Lack of Personnel Capability *** ** ** Little to no upfront costs (hardware and software) * * *** Not-so-powerful local machines * * * ***Note: Decision importance scale varies from project to projectRating ScaleScale CriteriaUnacceptable / Inappropriate* Marginal ** Acceptable / Possible*** Strong / Appropriate@USC CSSE 4University of Southern CaliforniaCenter for Systems and Software EngineeringWhat are the differences between each process?•Processes look similar•Different in detail and focus on different things•Based on your risks@USC CSSE 5University of Southern CaliforniaCenter for Systems and Software Engineering©USC-CSSEDifferent Risk Patterns Yield Different Processes@USC CSSE 6University of Southern CaliforniaCenter for Systems and Software Engineering@USC CSSE 7University of Southern CaliforniaCenter for Systems and Software Engineering@USC CSSE 8University of Southern CaliforniaCenter for Systems and Software Engineering@USC CSSE 9University of Southern CaliforniaCenter for Systems and Software Engineering@USC CSSE 10University of Southern CaliforniaCenter for Systems and Software Engineering@USC CSSE 11University of Southern CaliforniaCenter for Systems and Software Engineering@USC CSSE 12University of Southern CaliforniaCenter for Systems and Software Engineering@USC CSSE 13University of Southern CaliforniaCenter for Systems and Software EngineeringShould we select the process now? •The sooner you select the process, the better performance you will have–Spend less effort on unnecessary things–Make sure your client and you are on the same page–Open your eyes, ears  explore alternatives•BUT don’t rush–If not sure, do prototype, IKIWISI–Use COCOMO to calculate and compare resources–No analysis paralysis–What are the risks!!@USC CSSE


View Full Document

USC CSCI 577 - ec-16b_processes

Documents in this Course
ec-04

ec-04

39 pages

CSep15

CSep15

37 pages

ec-24

ec-24

42 pages

ec-11

ec-11

42 pages

ep10

ep10

6 pages

ec-07

ec-07

51 pages

ec-02

ec-02

22 pages

Load more
Download ec-16b_processes
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 ec-16b_processes 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 ec-16b_processes 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?