1 / 9

ITEC 370

This lecture focuses on the critical characteristics of well-defined software requirements and the concept of use cases. It outlines the process after compiling a requirements document, including formal presentations to clients and stakeholder involvement. Emphasis is placed on acceptance testing, showcasing how systems should function through scripted demonstrations, and the importance of agreement between developers and clients. Legal aspects surrounding software ownership and contracts are discussed, ensuring clarity in responsibilities, liabilities, and support. The goal is to enhance understanding for successful project delivery.

teneil
Download Presentation

ITEC 370

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITEC 370 Lecture 8 Requirements

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

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

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

  5. 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. 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. 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. 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. Review • Just because you know what to build doesn’t mean you are ready to start designing it

More Related