DOC PREVIEW
USC CSCI 577 - CritiqueGuidelines2009

This preview shows page 1 out of 3 pages.

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

Unformatted text preview:

Process Improvement (3/4 of emphasis)Product Improvement (1/4 of emphasis)Individual Critique Guidelines (160 Points)DEN studentsDue date; Friday December 11, 2009, 2:00 pmNo Hardcopy required; Softcopy; submit online thru DENOn-campus studentsDue date; Friday December 11, 2009, 2:00 pmHardcopy; outside of SAL 329; Softcopy; submit online thru DEN Submission Process:When submitting the softcopy, name it: Txx_FirstName_LastName.doc (for example, T01_ Scott_Chen.doc)Length:4-6 single-spaced pages (+/- a factor of 2) recommended, but not absolutely required. Don't use very small orlarge fontsMain Question:If you were to do the project over again, how would you do it better, and how does that relate to the softwareengineering principles in the course?The Individual Project Critique shall consist of the following two elements (more emphasis on element 1, i.e.,how the process could have been better?): Process Improvement (3/4 of emphasis)1. General Process ImprovementCandidate topics include but are not limited to: -Use of the Incremental Commitment Model-Use of various tools (Rational Software Modeler; USC-COCOMO II; COCOTS; DART; i-Studio; MS Project;templates; Bugzilla, etc.) -Class activities (team mixer, team formation, WinWin Negotiation, project kick-off meeting, tools tutorial,system architect special group meeting, and etc…)-System/Software Architecture Modeling (concepts, lectures, guidelines, applying the concepts to actualpractical modeling)-Information sources (lectures, papers, textbook, course notes, and etc...) -Human Resources (Professor, Guest Speakers, Teaching Assistant, clients, Library Personnel, ArchitectureReview Board members, DEN, and etc...) -Management (staffing, organization, planning, controlling process and product) -Special Roles (SRE, QFP, Shaper, Shaper assistant, and etc.) discuss the roles, how do you like it? Howshould we improve it?-Evaluation (Mid/End -semester evaluation, Individual critique, etc.)-Assignment (Individual Homework, Pre-class, In-class, Team Assignment, Post-class, etc)-Class Website (Structure, Content, Prefer to use DEN website, etc.)We would be particularly interested in feedback on the various tools and processes that is constructivein suggesting improvements rather than just identifying shortfalls; it should be balanced in identifying thingsthat were helpful as well as obstacles; and it should be relatively high-level in focusing on strategic factorsrather than individual bugs (turn in separate bug reports for that). 2. The Incremental Commitment Model Electronic Process Guide (ICM EPG)- Content of the guidelines for each case (content in each practice, roles, responsibilities, work products,delivery process, templates )- Use to the following decision criteria to evaluate your current project statuso Using the scale of 0 – 4,  0-Not Applicable / Definitely Not 1-Not really / Somewhat 2-Probably / May be 3- Presumably / Likely 4-Definitely / Certainly Decision Criteria Project Status(0-4)AlternativesYour final product has more than 30% of features available in application-based NDI/NCS Your final product has a single NDI/NCS that satisfies a complete solution Your final product has a very unique/ inflexible business processLife CycleYour project needs high control over upgrade / maintenance Your project needs rapid deployment; Faster time to marketArchitectureYour final project is critical on compatibility Your final product does not internet connectionYour final product needs high level of services / performance Your final product needs high security Your final product requires asynchronous communicationYour final product should be able to be accessed from anywhere ResourcesYour project has critical mass schedule constraints Your project lacks of personnel capability Your project requires little to no upfront costs (hardware and software) Your project requires low total cost of ownershipYour project has not-so-powerful local machines - The above decision criteria can be used to branch from one process pattern to another (such asArchitected Agile pattern to NDI-intensive pattern). o Is/Are there any other decision criteria that could be used to select/ branch a process pattern?o Is there any criteria that should be removed or may not contribute to pattern selection?3. WikiWinWin Tool- What were the strong and weak points of your team winwin negotiation?- What were the strong and weak points of the wikiwinwin tool?- Describe any improvement suggestions about the wikiwinwin tool, the negotiation process, and training?4. V&V Process - For evaluation process, and artifact review, were the V&V activities help you?- If you are a reviewer, were the team responsive to your concerns, how the team interacted with you?- Before the last two review packages, reviewers follow the workflow: Create Exit Criteria=>Review andReport=>Create Evaluation Report=>Track Issues, Which activity you think is the most helpful for yourproject and which is the least, any suggested changes to this process?- How do you feel Value-based V&V in the last two review packages? Does Value-based principle reallyimprove IIV&V process? Compared with the previous process, which one do you like? Why?- Suggested changes to the V&V process, how could the V&V process be improved to benefit your projectand your learning experience, etc.5. Team Assessment- Domain Knowledge Understandingo How well do you understand the client's business/domain?o What process did you use to model the client's business?- Staffing (Task assignments, Awareness of roles and responsibilities, Do you have the right people for thejobs? How do you determine whether he/she is right?)- Collaborations (Information sharing, Information synchronization)Product Improvement (1/4 of emphasis)Describe possible improvements in the various components of your product: i.e., if you had to design thesystem again, how would you do it better, knowing what you know now. The Product Improvement sectionwill not be considered in grading the final project, therefore, do not hesitate to discuss some of the potentialflaws of the current design: the CSCI 577b teams will consider product improvement suggestions during therebaselining of the Development Commitment package. The Product and Process improvement aspects of your Individual Critique may include the following: 1. Simplifier and Complicator Analysis: Identify


View Full Document

USC CSCI 577 - CritiqueGuidelines2009

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 CritiqueGuidelines2009
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 CritiqueGuidelines2009 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 CritiqueGuidelines2009 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?