|
|
| (3 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | == Planning - Discussion ==
| + | {{Review Instructions}} |
| − | Overall, the content is very good and appropriate. A few suggestions for improvement:
| |
| − | | |
| − | 1. Paragraph 5 (starting with "Task Planning...) - I suggest referring to "money" rather than "dollars" in the second line - (skills, equipment, facilities, money) - as BKCASE will have an international audience
| |
| − | | |
| − | 2. Good Practices # 5: Integrate risk management with the SE planning to identify areas that require special attention (for instance, prototyping or preferential development) and/or trades
| |
| − | | |
| − | 3. Good Practices # 6: The amount of management reserve should be based on the risk associated with the plan and cost and schedule impact of performing risk mitigation actions if triggered (refer to Waltzing with Bears here).
| |
| − | | |
| − | 4. Good Practice # 7: Use historical data for estimates and adjust for differences in scope or the development environment of the project (refer to COCOMO and COSYSMO here).
| |
| − | | |
| − | References: Add:
| |
| − | | |
| − | Boehm, B et al; "Software Cost Estimation with COCOMO II", Prentice Hall, ISBN 0-13-026692-2, 2000
| |
| − | | |
| − | DeMarco, T and Lister, T; "Waltzing with Bears; Managing Risks on Software Projects", ISBN 0-932633-60-9, Dorset House, 2003
| |
| − | | |
| − | Valerdi, R; "The Constructuve Systems Engineering Cost Model (COSYSMO); Quantifying the Costs of Systems Engineering Effort in Complex Systems", VDM Verlag Dr. Muller, ISBN 978-3-639-03478-3, 2008
| |
| − | | |
| − | (Input from Andy Pickard) (done, dho)
| |
| − | | |
| − | --
| |
| − | | |
| − | Brian Wells Comments: Materials and references are very good.
| |
| − | Write up is very good.
| |
| − | | |
| − | A SEMP and a SEP are not the same and the author should not say this in the article. SEP is a high level plan made before the system acquisition and development begin. It is written by the government customer. The SEMP is the specific development plan written by the developer (or contractor). The intent and content are quite different. SEP will have an acquisition plan, for example, that would not be included in a SEMP. (I can provide additional SEP and SEMP references if necessary.)
| |
| − | | |
| − | Figure that shows content of a SEMP should be reconfigured to fit the page better.
| |
| − | | |
| − | Has the author looked into and considered what is used in commercial SE development?
| |
Latest revision as of 20:22, 2 April 2022
Review Instructions
Please note that in order to provide review comments, you must first log in to the wiki. Please go to Login or create an account if you do not have a username (less than 1 minute).
Please provide your feedback on this article by responding to the specific discussion points below. In order to respond, please click “Reply” under the appropriate discussion thread. Feel free to read the comments of other reviewers as well (you may also respond directly to these comments). Please note that each article has a place for “Open Discussion” – please place any comments not related to the specific discussion points into this thread.
As the BKCASE author team develops SEBoK 0.75, they will provide an adjudication comment for each ‘‘thread’’ in the discussion – not each individual comment.
Note: We value community feedback and assume that all reviewers will respond in a professional manner. However, if any reviewer uses any form of profanity or consistently posts inflammatory comments or spam messages, that reviewer’s IP address will be blocked. To report any such problems, please email bkcase@stevens.edu.