Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

CS577b Spring 2008 RLCA Project Guidelines and Submission Instructions, Assignments of Aerospace Engineering

University of Southern California (USC)Aerospace Engineering

Guidelines and submission instructions for the rlca project in cs577b, a course offered in spring 2008. The project involves creating several artifacts, including an object-oriented class diagram, a system sequence diagram, an ssad and rsm zip file, a logical component diagram, a functional requirements document, a system use case diagram, a quality management plan, an iteration plan, a test plan and cases, and a peer review plan. The document also includes hints and references to help students complete the project.

Typology: Assignments

Pre 2010

Uploaded on 02/24/2010

koofers-user-ncw
koofers-user-ncw 🇺🇸

10 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
CS577b, Spring 2008
RLCA Draft (30 points)
Due: Friday February 8, 2008 at 2:00 pm
Submission Instruction: Upload to your team website; no hard copy
References:
-ec04b
-LeanMBASE Guidelines Version 1.9
-LeanMBASE template on the class website
Required Artifacts
OCD
SSRD
SSAD + RSM zip file
LCP
FRD
SID
plans
oQuality Management Plan
oIteration Plan
oTest Plan and Cases
oPeer Review Plan
Hints:
All of the guidelines for these documents can be found in LeanMBASE
-Quality Focal Point (QFP) person should start working from this point onward.
-OCD, SSRD, LCP and FRD: address and update all changes you might have, especially risk
lists in FRD document.
-SID: emphasize on trace from requirement to design
-SSAD Grading Guidelines
1) Background material (see leanMBASE guide), place in section 1 of support document.
2) System Analysis, equivalent to the Bookstore example (without the errors discussed)
that was presented in lectures, consisting of:
a) In the RSA Model :
i) A Domain/System Class Model
(1) Class Diagram(s) that show the information and artifacts that the system
needs, creates, or maintains.
(2) The description field of each class should describe it purpose.
(3) Any required attributes should be defined; but need not be shown on a
diagram. (You will not be penalized if you haven’t done this since I do not
think I made this clear in the past.)
ii) A System Process Model
(1) Use-case Diagram(s) that show the processes (e.g. Add Customer) in which
the system and external elements (people and other systems participate.
External elements should be shown as actors. Appropriate relations should
be shown.
(2) The description field of each actor should describe its purpose.
(3) The description field of each use-case should include:
(a) The overview of the process suitable for non-technical client without
design details (LCO);
(b) Any pre– or post–condition. (You can place pre– & post–conditions in the
MS Word support document if you prefer).
b) In MS Word, Section 2 include:
i) A summary of System Analysis results & key concepts (e.g. important classes,
critical or risky processes);
ii) A rationale, especial for any refinements of OCD (e.g. which stakeholders are
operational).
pf2

Partial preview of the text

Download CS577b Spring 2008 RLCA Project Guidelines and Submission Instructions and more Assignments Aerospace Engineering in PDF only on Docsity!

CS577b, Spring 2008 RLCA Draft (30 points) Due: Friday February 8, 2008 at 2:00 pm Submission Instruction: Upload to your team website; no hard copy References:

- ec04b - LeanMBASE Guidelines Version 1. - LeanMBASE template on the class website Required Artifacts  OCD  SSRD  SSAD + RSM zip file  LCP  FRD  SID  plans o Quality Management Plan o Iteration Plan o Test Plan and Cases o Peer Review Plan Hints: All of the guidelines for these documents can be found in LeanMBASE - Quality Focal Point (QFP) person should start working from this point onward. - OCD, SSRD, LCP and FRD: address and update all changes you might have, especially risk lists in FRD document. - SID: emphasize on trace from requirement to design - SSAD Grading Guidelines

  1. Background material (see leanMBASE guide), place in section 1 of support document.
  2. System Analysis, equivalent to the Bookstore example (without the errors discussed) that was presented in lectures, consisting of: a) In the RSA Model : i) A Domain/System Class Model (1) Class Diagram(s) that show the information and artifacts that the system needs, creates, or maintains. (2) The description field of each class should describe it purpose. (3) Any required attributes should be defined; but need not be shown on a diagram. (You will not be penalized if you haven’t done this since I do not think I made this clear in the past.) ii) A System Process Model (1) Use-case Diagram(s) that show the processes (e.g. Add Customer) in which the system and external elements (people and other systems participate. External elements should be shown as actors. Appropriate relations should be shown. (2) The description field of each actor should describe its purpose. (3) The description field of each use-case should include: (a) The overview of the process suitable for non-technical client without design details (LCO); (b) Any pre– or post–condition. (You can place pre– & post–conditions in the MS Word support document if you prefer). b) In MS Word, Section 2 include: i) A summary of System Analysis results & key concepts (e.g. important classes, critical or risky processes); ii) A rationale, especial for any refinements of OCD (e.g. which stakeholders are operational).

(Note: include diagrams or references to diagrams from the Model as needed to support your summary & rationale; but you do not need to include every diagram.)

  1. Design, equivalent to the examples shown during lectures, consisting of: a) In the RSA Model : i) A Deployment Model that shows the architecture of your system, including (1) The SW components (RSA uses UML2's "artifact" notation in Deployment diagram -- either artifact or ordinary component notation is acceptable), (2) Their connections, (3) Their allocation to hardware; ii) An Information Model that includes: (1) the classes (i.e. entity, boundary, control classes) are designed to implement the information and artifacts identified in the System Analysis, as well as any classes identified while prototyping and while describing the implementation (realized) of the use–cases. (2) Any operations or attributes of the classes identfied while prototyping and while describing the implementation (realized) of the use–cases. (The operations and attributes may be shown on a diagram or just in the property list of the class.) iii) A Process Realization Model, including (1) An Use-case Realization Diagram(s) that show the use–case realization of the system processes; (2) A textual description, for non-technical client, with nominal & alternate courses of action plus details from prototype for each process; (you may put this in the support document if you prefer.) (3) A sequence diagram for 1 or 2 processes that are high risk or that involve many components (the goal is to show that your architecture works, i.e. that the architecture can implement the required processes). b) In MS Word, Section 3 and/or 4 include : i) A summary of your design results , including: (1) Your architecture, (2) key concepts (e.g. important classes, critical or risky processes), (3) Any patterns, frameworks (e.g. Java Relation Database framework), or COTS products used; ii) A rationale for your design, explain: (1) Your decision about doing TIM and/or TSM (2) Your selection of components, patterns, frameworks, and COTS products. (3) How your design satisfies your requirements (inc. LoS) (Note: include diagrams or references to diagrams from the Model as needed to support your summary & rationale; but you do not need to include every diagram.) UML errors will only be deducted from the RSA model; although you may loose points in the Word Supplement document that may be attributable to the UML if the summary or explanation of your design is not consistent with your model.