The System Specification

1. The System Specification And the vagueness of our process

2. The problem statements as presented • Give far too little information • Are inadequate as stated for grade-able projects • Must be expanded, solidified, identified, researched • A good problem statement must emerge

3. The whole purpose of the project • Invent something that has not been invented. • Improve the quality of life of the severely handicapped, their teachers and therapists. • We cannot tell you what to do, because that would stifle the creativity.

4. Phase 2 of the Project • Write a system specification • You are the customer • You represent the users • You have money to spend and are trying to guarantee value

5. Taoist Principle #11: Turn non-being into utility In the Tao, the concept of the uncarved block indicates that emptiness (non-being) has usefulness. Just as the space in a bowl, and the vacant places of doorways serve important functions, ideas of non-being can help engineers. The teacher who asks a question and then does nothing actually does something very useful in providing time for students to think. The concept of “reading between the lines” shows that there is something where there is nothing. “Something comes from nothing, nothing comes from something.”

6. Apply this • Define the problem at its simplest, base level. • Be clear on what is the foundation, and what are extras. • Be simple, clear, and concise. • Use experience with no loyalty. • Be exceptionally creative. • Integration Thread

7. The Way is elusive but real, intuition leads. • Be cautious, reserved, flexible, sincere, honest. • Control input to the senses, avoid confusion and respond to inner depth – build a good GUI. • Have faith in others so they will have faith in you – real teamwork.

8. Do not see things in black and white. • Progress is slow, do not boast. • Discipline yourself before trying to discipline others. • Avoid using force, do not push – if the solution does not unfold easily, it is the wrong solution. • Seek simplicity. Do not indulge in excess – uncomplicate your design.

9. When you don’t know, say so. • Pu’ – the uncarved block – build incrementally. • The Wu-Wei – without effort – the most natural solution will present itself. • The Wu-Wei - without resistance – on your team, avoid meddlesome, combative, or egotistical effort.

10. Now, phase 2 • Get your MSDNAA subscription going • Your MSDNAA Online Software System can be found at: http://msdn04.e-academy.com/ub_csemanagement Your username is : your email address Your password is : ******** Write to cse-consult@buffalo.edu • Update your web page • Define project deliverables – what is your customer expecting? • Due date

11. Title Page (accurate) Table of Contents Introductory Problem Statement History / Research / Current Solutions / Deficiencies of current solutions (if applicable) Proposed Solution (optional) - from the domain perspective Objectives / Goals – Relevance & Quality of Life Functional Requirements - detail everything that the system has to do. e.g. Interface between user & system, and more User Profile / Deployment Environment / Who will use the system? The system may be used by both a client, and therapist, or family members. There may be many users. Constraints – budget, schedule, technical (note: not a budget or schedule, but constraints) Project Deliverables Future Plans and Expandability System Spec Topics

12. Due date – ????? • Leave 4 weeks for phase 5 • Leave 1 week for phase 4 • Leave at least 3 weeks for phase 3 • Submit on your web site • Phase 2 – Requirements - 10/1 - 10/16 ??? • Midterm: 10/17 or thereabouts • Phase 3 – Design – 10/18 - 10/31 • Phase 4 – Program Plan – 11/1 - 11/7 • Phase 5 – 11/8 - 12/2 • Demos – 12/2 -12/9

13. A few pointers on Phase 2 • Research the domain extensively. • Make sure it's a problem to be solved, more than description of a system • Do not lean toward a specific solution. General tendency toward software/computers is unavoidable. • Research the domain extensively.