1 / 16

Development of the Software Clicker

A Group Project in Software Engineering II Fall 2011. Development of the Software Clicker. Software Clicker (1 of 2). Software Requirements Summary

bjorn
Download Presentation

Development of the Software Clicker

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. A Group Project in Software Engineering II Fall 2011 Development of the Software Clicker

  2. Software Clicker (1 of 2) • Software Requirements Summary • Create a client program and a server program in which the server sends a series of questions and multi-choice answers to each client, the client gathers student responses to each question and sends the answers back to the server, and the server tabulates the answers and displays the results on its screen • All questions and answers are read by the server from a formatted text file and stored in the program before use. The questions shall be presented to the client either one at a time (single mode) or in a group (quiz mode) • All displays are text based • Project Start Date: Monday, Oct. 3, 2011 • Project Stop Date: Friday, Nov. 11, 2011

  3. Software Clicker (2 of 2) • Programming Language and Compiler • Sun Java 1.6 or higher (no extensions‏) • Initial Implementation Constraints • Software shall run on a desktop, laptop, or netbook computer running 32-bit Windows, Linux, or Mac OS • Software shall communicate over a stand-alone wired LAN consisting of a router and a switch. The LAN shall have one computer running the server software and one or more other computers, each running the client software • No source code dependency shall exist for any specific platform or operating system except as stated above • No dependency shall exist on any integrated development environment (IDE) for coding, testing, or software execution

  4. Organizational Chart Software Engineering Directorate Dr. Tevis Project Management * Bob Charney Requirements Management * Tim VanDorenFrancis Isibor SoftwareDesign * Andrew HoosDerek Swager Quality Assurance * Paul BratteliBilly Smith SoftwareConstruction* John CronkiteScott GeigelDustin Masters Configuration Management(Contractor)

  5. Object-Oriented Requirements Analysis Object-Oriented Design (Architectural) Object-Oriented Design (Component-level) Software Construction Validation and System Testing Software Delivery Software Development Life Cycle Model (1 of 3)

  6. Software Requirements Review (SRR) Preliminary Design Review (PDR) Critical Design Review (CDR) Test Readiness Review (TRR) Test Outcome Review (TRR) and FCA/PCA Software Development Life Cycle Model (2 of 3)

  7. Object-Oriented Requirements Analysis Object-Oriented Design (Architectural) Object-Oriented Design (Component-level) Software Construction Validation and System Testing Software Delivery Software Requirements Review (SRR) Preliminary Design Review (PDR) Critical Design Review (CDR) Test Readiness Review (TRR) Test Outcome Review (TRR) and FCA/PCA Software Development Life Cycle Model (3 of 3)

  8. Requirements and Testing Table • 14 general requirements • 37 server internal requirements • 12 client internal requirements • 7 server interface requirements • 9 client interface requirements------ 79 test cases

  9. UML Class Diagram for the Server Server ServerManager ServerData NetworkManager ExportManager ScreenManager ResponseManager QuestionManager Question Response ResponseResult

  10. UML Class Diagram for the Client Client ScreenManager ClientManager NetworkManager QuestionManager Question

  11. Technical Review Meetings (17 over a 6-week Period)

  12. Configuration Management 20 baselined artifacts 497 lines of Server source code 311 lines of Client source code

  13. Project Website http://www.letu.edu/people/jaytevis/Software-Engineering/Fall-2011-Group-Project/index.html

  14. System Configuration for the Software Clicker Student (Client) Student (Client) Student (Client) Router/Switch Student (Client) Student (Client) Student (Client) Student (Client) Instructor (Server)

  15. Software Demonstration

More Related