1. COSC 4303 Software Engineering Introduction and Initial Planning of Group Projects Fall 2007

2. Organizational Structure Software Engineering Directorate Tevis Software Development DAT Team Bruning Malone (Wall) RubyRed Team Hadfield O’Grady Palermo Configuration Management Tevis Quality Assurance and Testing Elworth Bracy Glidden Kreis Requirements Management Baustian Chase Shaw (Wall) Project Management Rice Special Projects Bradbury

3. Update software development plan (SDP) Create OORA model (SRS) Software Requirements Review (SRR) Create architectural design model (SDD) Preliminary Design Review (PDR) Create component- level design (SDD) Create source code and do unit testing Critical Design Review (CDR) Do product build and integration testing Test Readiness Review (TRR) Do validation testing Create software version description (SVD) Determine qualification methods for requirements (STP) Create user interface design (SDD) Create preliminary software development plan (SDP) Task Network for the Organizational Software Development Process (Version 1) Create validation test cases (STD) Identify and record detailed software requirements (SRS) Deliver product and documentation Functional and Physical Configuration Audits (FCA/PCA) Note: If formal approval does not occur at a review or audit, this will require a return to a previous non-review step in the process Discuss software needs and project scope with customer Test Outcome Review (TOR)

4. Organizational Responsibilities (1 of 3) Software Engineering Director –Provide oversight for all of the company’s software engineering projects –Serve with the Customer Director as the review and project approval authority –Act as the baselining authority for all project documents and software –Moderate the SRR, PDR, CDR, TRR, TOR, FCA/PCA, and product delivery Project Management (PM) –Construct a timeline chart for each assigned project –Maintain timeline chart and brief the current status of each project –Report any project abnormalities, problems or delays to the Software Engineering Director –Collect any baselined products from Software Development –Submit any baselined products to Configuration Management Requirements Management (RM) –For each project, identify and record all user software requirements in a requirements table –Maintain the integrity of each requirements table by tracking any additions, changes, and deletions to the requirements table and submitting baselined versions to Configuration Management –Assist Quality Assurance in the validation testing of the software –Act as the customer representative at all review and audits Configuration Management (CM) –Provide configuration management services for all baselined artifacts –Maintain a project website of baselined artifacts

5. Organizational Responsibilities (2 of 3) Software Development –Based on the user software requirements, create an object-oriented requirements analysis model –Present this model at the Software Requirements Review (SRR) –Submit the baselined OORA model to your PM –Transform baselined OORA model into an OO architectural design model –Present this model at the Preliminary Design Review (PDR) –Submit the baselined architectural design model to your PM –Expand the baselined architectural design into a user interface design model and a component- level design model –Present these models at the Critical Design Review (CDR) –Submit the baselined user interface and component-level design models to your PM –Translate the baselined design models into source code and perform unit testing –Perform a product build and do software integration testing –Present the source code and your unit and integration testing results at the Test Readiness Review (TRR) –Submit the baselined source code to your PM –Provide assistance to QA during validation testing of the software –Based on the test results, make any necessary changes to the software to create a corrected version –Present the corrected source code at the Test Outcome Review (TOR) –Submit the baselined corrected source code to your PM –Create a software version description (SVD) –Present your software product specification at the Functional/Physical Configuration Audit (FCA/PCA) –Submit your baselined SVD to your PM

6. Organizational Responsibilities (2 of 3) Quality Assurance and Testing (QA) –For each assigned project, determine the qualification method to be used for each requirement listed in the baselined requirements table –Based on the qualification method, create a validation test case for each requirement listed in the baselined requirements table –Before validation testing begins, obtain the baselined source code from Configuration Management –With the assistance of Requirements Management and Software Development, perform validation testing of the software requirements and record all results in the requirements table –Coordinate with Software Development to make any changes to the software in order to create a corrected version –Present the validation test results, as recorded in the requirements table, at the Test Outcome Review (TOR) –Submit the baselined requirements table to your PM

7. Format of User Requirements Table Req. IDRequirement Description Qual. Type Input Data Expected Output Actual Output Passed Test?

8. DAT Project Software Requirements: Software tool to perform Discourse Analysis (developed by Dr. James Price) Contacts: Tim Brittain Programming Language: ?

9. RubyRed Project Software Requirements: User interface for user management, hosting account information, ticketing system, mail management, FTP management, web statistics integration, and administration Contacts: Tim Dyck, Colin Calvert Programming Language: Ruby on Rails More information: http://newton.gottathink.com/projects/gt- cp/roadmaphttp://newton.gottathink.com/projects/gt- cp/roadmap