1. ITEC 370 Lecture 8 Requirements

2. Review Requirements –What are some of the characteristics of a good requirement? –What are use cases?

3. Requirements Objectives Today –1 page single spaced 12 pt font description of your idea What to do after you have the requirements document…

4. Requirements Presentatio n Present what you are going to build to the client Invite the stakeholders Formal meeting Short intro / motivation Features Interfaces

5. Requirements Acceptance testing Have description of how system is supposed to work Need –Software that implements the requirements document –A way for you and the client to agree that the delivered software works as expected

6. Requirements Acceptance testing Users need to see the software working Could just send a.exe and say done… Better way –Scripted demonstration –Pre-determined –Trial period for usage

7. Requirements Issues Lawyer needed –Serious contract issues can arise When is it “completed” After software is built who owns it? –Source code vs binaries Tech-support / Maintenance support Updates to the project

8. Requirements Sample contract Sections –Duties and responsibilities –Ownership of software –Compensation –Are you employees or independent contractors for the company (tax issues) –Customer monitoring –Change in specifications –Confidentiality –Training –Warranty –Term / Termination –Contact between developer and client –Waivers (if you forego one part of the contract, you don’t give it all up) –This contract is it, no previous agreements

9. Requirements Review Just because you know what to build doesn’t mean you are ready to start designing it