RAP Software Process Checklist

Transcription

1 RAP Software Process Checklist It is recommended that every RAP project fill out the project checklist on a regular basis to make software process a consciousdecision. The purpose of this checklist is to ask some software project process and practices questions to stimulate thinking. Much of software process and practice is about making conscious choices. There are no right or wrong answers to the following questions; they are intended to foster discussion by the project team and be a guide for areas to consider. It is entirely expected that different projects will need and use very different levels of software process and practices. A list of related sources is included at the end of this file for additional information. Initial project information 1. Project name: 2. Type of project: field program research prototype operational 3. Size of project (resources): small (1-2 people) medium (2-10 people) large (10+) 4. Size of project (scale): small (1000 lines of code or less) medium ( ,000 lines of code) large (10, ,000 lines of code) really big (>100,000 lines of code) 5. Length of project: short (1 month or less) medium (1 month - 1 year) long (> 1 year) ongoing 6. Identify project user/customer:

2 7. Deliverables (check all that apply)? documents/reports running system algorithm descriptions user training manuals 8. User/customer support? 24/7 regular business hours only 9. Level of user/customer interaction with project team (check all that apply) frequent infrequent 10. Level of user/customer training (check all that apply)? classes site visits manuals 11. List the project's main goals for the year Overall project process 1. Rank the following 3 items in terms of their importance on this project. You must rank the items, no ties. (1) Minimize defects (e.g., more reliable, fewer bugs) Maximize customer satisfaction (e.g., custom software) Minimize cost

3 2. Software life cycle model? "A software lifecycle is a model that describes all the activities that go into creating a software product. Product development styles vary tremendously among different kinds of projects, requiring different kinds of tasks and different task orderings." (2) waterfall (document driven, linear, defined requirements) code-and-fix (informal, no planning or documents) spiral (risk-oriented model, refinement of waterfall model) evolutionary (develop prototype and refine until acceptable) staged delivery (deliver in successive stages) design-to-schedule (prioritize features, do highest priority first) 3. Software development process model? XP (Extreme Programming, see agile (see CMM (see 4. Are project engineering meetings scheduled on a regular basis? If so, how often are they scheduled? monthly biweekly weekly as necessary 5. Requirements management? "Requirements management is the process of gathering requirements; recording them in a document, , UI storyboard, executable prototype or some other form; tracking the design and code against them; and then managing changes to them for the rest of the project" (3) (e.g., tracking changes to requirements) 6. Some level of risk management? "The job of software risk management is to identify, address, and eliminate sources of risk before they become threats to successful completion of a software project." (4) crisis management (i.e., firefighting) risk mitigation (i.e., plan ahead for risks)

4 7. Monitor project progress? milestones MSProject status meetings 8. Will the project undergo an internal periodic assessment (e.g., goals achieved, analysis of past year)? 9. Project measurement/metrics (e.g., estimates vs. actual) Project practices 1. Will this project use version control? CVS 2. Will this project do bug tracking? Bugzilla 3. Code reuse? minimal, expect to write mostly new code moderate, expect to use existing code for 50% of project high, expect to use existing code for 75% of project very high, expect to use existing code for >75% of project 4. Will this project do automated builds? yes no 5. Will the results of automated builds be communicated automatically to the team? yes no

5 6. Will this project do data archive? disk tape optical media NCAR Mass Storage System 7. Will this project use/develop a playback capability? use existing (e.g., MDV servers) develop new 8. Will this project do formal testing? (see ) unit testing ( regression testing integration testing GUI testing 9. Will the project use a design protocol? UML design reviews documents 10. Will this project do releases? (e.g., provide CDROM and install scripts) 11. Will this project do verification?? 12. Will this project do validation??

6 Project practice technical details 1. What data formats will the project use? MDV SPDB GRIB netcdf MB MD/MF SQL ASCII 2. What platforms will the project use? Debian Linux RedHat Linux Sun Solaris SGI Windows 3. What languages will the project use? C C++ FORTRAN Java Perl Python Matlab others 4. What infrastructure will the project use? 4a. Process control auto_restart ctpm cron 4b. Configuration file reading TDRP CFRD XML

7 4c. Data file distribution DsFileDist md_rep scp NFS rsync 4d. Logging LE LOG javalog 4e. Visualization CIDD NCAR Graphics datacanvas RDI zebra VMET web image files 5. What documentation formats will the project use? MSWord HTML DocBook javadoc pydoc PowerPoint 6. What development tools will the project use? JBuilder purify insure Footnotes: (1) "Practical Software Metrics for Project Management and Process Improvement", Robert B. Grady, Prentice-Hall, 1992, p.24 (2) "Rapid Development", Steve McConnell, Microsoft Press, 1996, p.465

8 (3) "Rapid Development", Steve McConnell, Microsoft Press, 1996, p.61 (4) "Rapid Development", Steve McConnell, Microsoft Press, 1996, p Related sources: URL's: Video training tapes available at RAP: 1 Software Engineering Overview 2 Software Project Management 3 Information Engineering 4 Reengineering Techniques 5 Object Oriented Methods 6 Software Testing 7 Software Quality Assurance 8 Software Configuration Management