diff --git a/Features.md b/Features.md
index 192e13a..48a52ce 100644
--- a/Features.md
+++ b/Features.md
@@ -44,7 +44,7 @@ Risk: ::Safe
Functional area(s): ::Administration
-Use case(s): ::[UC-00](use-cases#UC-00) [UC-11](use-cases#UC-11)
+Use case(s): ::[UC-00](Use-Cases#UC-00) [UC-11](Use-Cases#UC-11)
Description:
@@ -68,7 +68,7 @@ Risk: ::Safe
Functional area(s): ::Administration
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
:: Visitors can come to the site and register themselves. They must provide the following information:
@@ -103,7 +103,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
:: 1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
@@ -129,7 +129,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -156,7 +156,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -184,7 +184,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -212,7 +212,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -239,7 +239,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -267,7 +267,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -295,7 +295,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -323,7 +323,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -351,7 +351,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -378,7 +378,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -406,7 +406,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -434,7 +434,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
@@ -462,7 +462,7 @@ Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
Functional area(s): ::WORD, WORD, WORD
-Use case(s): ::[UC-01](use-cases#UC-01)
+Use case(s): ::[UC-01](Use-Cases#UC-01)
Description:
diff --git a/Resource-Needs.md b/Resource-Needs.md
index c57e931..538e7f1 100644
--- a/Resource-Needs.md
+++ b/Resource-Needs.md
@@ -10,7 +10,7 @@
##### Related Documents:
- [Project proposal](Proposal)
- [Project plan](Project-Plan)
-- [QA plan](qa-plan.html)
+- [QA plan](QA-Plan)
- [Software development methodology](SDM)
- [Glossary](Glossary)
---
diff --git a/Review-Meeting-Checklists.md b/Review-Meeting-Checklists.md
index 4f349b1..2ca391b 100644
--- a/Review-Meeting-Checklists.md
+++ b/Review-Meeting-Checklists.md
@@ -1,24 +1,3 @@
-
-
-
-
-
- ReadySet Markdown
-
-
-
-
-
- Overview
- Project Plan
- Workflows
-
-
-
-
-
-
-
# Review Meeting Checklists
---
@@ -39,24 +18,3 @@
- ::[More C++ style guides](http://directory.google.com/Top/Computers/Programming/Languages/C%2B%2B/Style/)
- ::[More Java style guides](http://directory.google.com/Top/Computers/Programming/Languages/Java/Coding_Standards/)
- ::[Python PEP 8 style guide](https://www.python.org/dev/peps/pep-0008/)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/Review-Meeting-Notes.md b/Review-Meeting-Notes.md
index 158408c..ba01c8a 100644
--- a/Review-Meeting-Notes.md
+++ b/Review-Meeting-Notes.md
@@ -1,27 +1,3 @@
-
-
-
-
-
- ReadySet Markdown
-
-
-
-
-
- Overview
- Project Plan
- Workflows
-
-
-
-
-
-
-
-# [QA Plan](qa-plan.html) > Review Meeting Notes
----
-
##### Project:
::[PROJECTNAME](Home)
@@ -42,15 +18,15 @@
- ::PERSONNAME
##### Related documents:
-
-- [Review Meeting Checklists](review-meeting-checklists.html)
+- [QA Plan](QA-Plan) > Review Meeting Notes
+- [Review Meeting Checklists](Review-Meeting-Checklists)
---
### Documents and Code Reviewed at this Meeting
-- ::[Feature list section of requirements](requirements.html#functional)
-- ::[Multi-user section of requirements](requirements.html#multiuser)
+- ::[Feature list section of requirements](#)
+- ::[Multi-user section of requirements](#)
- ::[Hello.java](/source/browse/PROJECTNAME/src/Hello.java)
- ::[HelloStream.java](/source/browse/PROJECTNAME/src/HelloStream.java)
- ::[HelloPanel.java](/source/browse/PROJECTNAME/src/HelloPanel.java)
@@ -84,25 +60,3 @@ inspected, it still needs review.
::All defects and tasks identified in this review are being tracked in the
issue tracker.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/Risks.md b/Risks.md
index 242b753..5809ffc 100644
--- a/Risks.md
+++ b/Risks.md
@@ -1,27 +1,3 @@
-
-
-
-
-
- ReadySet Markdown
-
-
-
-
-
- Overview
- Project Plan
- Workflows
-
-
-
-
-
-
-
-# Risks
----
-
##### Project:
::[PROJECTNAME](Home)
@@ -35,6 +11,7 @@
##### References:
- [Risk Management during Requirements](http://www.systemsguild.com/pdfs/s5req.lo%201.pdf) by Tom DeMarco and Tim Lister
- [Taxonomy-Based Risk Identification](http://www.sei.cmu.edu/pub/documents/93.reports/pdf/tr06.93.pdf) by Carr, Konda, Monarch, Ulrich, and Walker (SEI)
+
---
**Process impact:** This document records the major project risks, and
@@ -52,12 +29,78 @@ plans to control them. For each risk the plan should include:
general contingency plans. In this case you only need to give a
contingency plan if you have a special one for the particular risk.
-The severity of a risk is its likelihood multiplied by its impact. Risks
-are classified as minor if they have low likelihood, negligible impact,
-or medium likelihood and marginal impact.
+The severity of a risk is its likel
+##### Project:
+::[PROJECTNAME](Home)
-*TODO: You should update these lists regularly. They should be reviewed
-by customers and developers from time to time.*
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+---ihood multiplied by its impact. Risks
+are classified as minor if they hav
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+---e low likelihood, negligible impact,
+or medium likelihood and marginal i
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+---mpact.
+
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+---
+*TODO: You should update these list
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+---s regularly. They should be reviewed
+by customers and developers from ti
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+---me to time.*
### General contingency plans
@@ -95,7 +138,7 @@ delivery date.
|-----------------|---------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------|
| ::Requirements | Requirements are only partly known at project start. Customers may not allocate sufficient resources to exploring requirements. | Medium | Critical to Catastrophic | Requirements will be detailed first for the top priority goals. Indicator: Track the rate at which requirements are discovered. Contingency: request more customer effort. | Amber | Requirements Lead |
| ::Goals | Stakeholders goals may conflict. | Medium | Critical | Keep an explicit list of stakeholders goals. The project manager will report progress to each declared goal. | Green | Customers |
-| ::Communication | Communication problems in development team. They are dispersed among several sites, and have not worked together before. | Medium | Critical | Use these [tools](sdm#communication) to help communication. The main indicator of miscommunication will be software defects detected by our [QA activity](qa-plan). | Green | QA lead |
+| ::Communication | Communication problems in development team. They are dispersed among several sites, and have not worked together before. | Medium | Critical | Use these [tools](SDM#communication) to help communication. The main indicator of miscommunication will be software defects detected by our [QA activity](qa-plan). | Green | QA lead |
| ::Acceptance | Customer may accept delivery of the system although it does not really meet their goals. | Medium | Critical | Customers are asked to declare acceptance criteria as each release is planned. | Green | Customers |
| ::Scope | The total features requested may be beyond what the development team can deliver in the time available. | High | Marginal | Assign levels of important to the use cases. Make the first review of project scope after 12 months. | Green | Customers |
@@ -108,11 +151,99 @@ impact of a risk has increased to make it a "major" risk.*
|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------|
| ::Estimate | The development team might not be able to estimate the work time, preventing customers from deciding priorities effectively. | Medium | Marginal | The development team will gain experience in estimating the work, and deliver the first estimates after 12 months. We will compare estimated work to actual work. | Green | Project Manager |
| ::Retention | Some developers may leave the project before it is finished. | Medium | Marginal | Employing locations should provide support for continuing professional development. The project manager will discuss career goals with each developer, and try to assign tasks appropriately. | Green | Project Manager |
-| ::Correctness | The system as delivered may have low take-up because of a lack of confidence in its correctness. | Low | Catastrophic | State of the art [QA activity](qa-plan). Contingency: stop development of new facilities until the quality of the existing code is assured. | Green | QA Lead |
-| ::Usability | The system as delivered may have low take-up because of poor usability. | Low | Critical | We will have a UI style guide. Most of the development of the front end will be in close contact with customers. We will review usability later in the project. | Green | UI design lead |
+| ::Correctness | The system as delivered may have low take-up because of a lack of confidence in its correctness. | Low | Catastrophic | State of the art [QA activity](QA-Plan). Contingency: stop development of new facilities until the quality of the existing code is assured. | Green | QA Lead
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+--- |
+| ::Usability | The system as
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+--- delivered may have low take-up because of poor usability.
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+--- | Low
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+--- | Critical | We will have a UI style guide. Most of the development of the front end will be in close contact with customers. We will review usability later in the project. | Green | UI design lead |
| ::Desire | The stated requirements might not match the customers' desires and ambitions for the system. | Low | Critical | Incremental delivery of versions will provide experience of using the system, which will help the customers to identify the real requirements. Indicator: a developer saying "I think they mean ...", a customer saying "They know what I mean". Contingency: request customer review of requirements. | Green | Customers |
-| ::Changes | After requirements have been documented and agreed, development activities begin to based on them, first design then implementation. If the requirements change later then effort is wasted. | Low | Critical | A change control procedure is required, so changes are only made when the cost is worthwhile. Indicator: compare cost of change to new development. Contingency: request customer review of requirements. | Green | Project Manager |
-| ::Process | Some developers may not cooperate in common standards and processes. | Low | Critical | QA to check conformance, then discussions in development team meetings to change the standard or the actual practice as appropriate. | Green | QA Lead |
+| ::Changes | After requirements have been documented and agreed, development activities begin to based on them, first design then implementation. If the requirements change later then effort is wasted. | Low | Critical | A change control procedure is required, so changes are only made when the cost is worthwhile. Indicator: compare cost of change t
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+---o new development. Contingency: request customer review of requirements.
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+--- | Green | P
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+---roject Manager |
+| ::Process | Some develope
+##### Project:
+::[PROJECTNAME](Home)
+
+##### Internal Release Number:
+::X.Y.Z
+
+##### Related Documents:
+- [Proposal](Proposal) > Target Audience and Benefits
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [Glossary](Glossary)
+---rs may not cooperate in common standards and processes. | Low | Critical | QA to check conformance, then discussions in development team meetings to change the standard or the actual practice as appropriate. | Green | QA Lead |
| ::Maintainability | The system as delivered might be hard to maintain. | Low | Marginal | We will review the code for maintainability. | Green | Lead Developer |
| ::RISKNAME | ONE-TO-THREE-SENTENCES | Low or Medium or High | Negligible or Marginal or Critical or Catastrophic | ONE-TO-THREE-SENTENCES | Red or Amber or Green | PERSONNAME |
@@ -130,7 +261,7 @@ Not yet active
### Risk Checklist
#### Do the plans provide an indicator to detect each of the risks becoming active?
-::Yes, if all activies are carried out as planned, we will know if any
+::Yes, if all activities are carried out as planned, we will know if any
of the risks is becoming troublesome.
::No, some risks could creep up on us.
@@ -180,25 +311,3 @@ the project could deliver.
::No, everything depends on the alertness and strength of character of
the project manager.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/SDM.md b/SDM.md
index f763a9d..fdcce2f 100644
--- a/SDM.md
+++ b/SDM.md
@@ -1,51 +1,5 @@
-
-
-
-
-
- ReadySet Markdown
-
-
-
-
-
- Overview
- Project Plan
- Workflows
-
-
-
-
-
-
-
-# Software Development Methodology
----
-
*TODO: This template is not done yet. Feel free to contribute your ideas.*
A Software Development Methodology is always specific to a given
company, but the outline of that document could be reused, as could some
-sections on common practices such as version control procedures.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+sections on common practices such as version control procedures.
\ No newline at end of file
diff --git a/SRS.md b/SRS.md
index 3af18d4..09233b8 100644
--- a/SRS.md
+++ b/SRS.md
@@ -1,27 +1,3 @@
-
-
-
-
-
- ReadySet Markdown
-
-
-
-
-
- Overview
- Project Plan
- Workflows
-
-
-
-
-
-
-
-# Software Requirements Specification
----
-
##### Project:
::PROJECTNAME
@@ -41,10 +17,10 @@
**Process impact:** The SRS precisely defines the software product that
will be built. Decisions made in writing the SRS are based on
-information in the [project proposal](proposal) and [user
+information in the [project proposal](Proposal) and [user
needs](User-Needs) documents. The SRS sets requirements that must
-be satisfied by the [system design](design). The SRS is verified
-and validated by activities outlined in the [QA plan](qa-plan.html).
+be satisfied by the [system design](Design). The SRS is verified
+and validated by activities outlined in the [QA plan](QA-Plan).
### Introduction
@@ -273,25 +249,3 @@ Details:
- ::The system will read and write valid .XYZ files used by
OTHER APPLICATION
- ::DETAIL
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/Status-Report.md b/Status-Report.md
index c83fefa..09479fc 100644
--- a/Status-Report.md
+++ b/Status-Report.md
@@ -67,8 +67,71 @@ words.
::Two major problems have been uncovered...
-::We are approximately 30% of the way through the project plan, and
-running about 2 days ahead of schedule...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+