Software Engineer Deliverable
Social Campus Hangout
Deliverable 4
Florida International University
School of Computing and Information Sciences
CIS 4911 Senior Capstone Project – Software Engineering Focus
Cesar Vega
Mentors: Dr. Tao Li, Lei Li
Table of Contents
- Introduction
1.1. Problem definition.
1.2. Scope of system.
1.3. Over all development methodology.
1.4. Definitions, acronyms, and abbreviations
1.5. Overview of document
- Feasibility Study
2.1. Description of current system.
2.2. Description of alternative solutions considered.
2.3. Recommendation with explanation of why the solution was selected.
- Project Plan
3.1. Project Organization
3.1.1. Project Personnel
3.1.2. Hardware and Software Resources
3.2. Identification of Tasks, Milestones and Deliverables
3.3. Cost of the Project
- System Requirements
4.1. Functional and Nonfunctional Requirements
4.2. Requirements Analysis
- System Design
5.1. Overview
5.2. Subsystem Decomposition
5.3. Hardware and Software Mapping
5.4. Persistent Data Management
5.5. Security/Privacy
- Detailed Design
6.1. Overview
6.2. Static model
6.3. Dynamic model
6.4. Code Specification
- System Validation
7.1. System Tests
7.2. Evaluation of Tests
- Glossary
- Appendix
9.1. Appendix A – Project schedule (Gantt chart or PERT chart).
9.2. Appendix B – All use cases with nonfunctional requirements.
9.3. Appendix C – User Interface designs.
9.4. Appendix D – Analysis models (static and dynamic)
9.5. Appendix E – Design models (static and dynamic)
9.6. Appendix F – Documented Class interfaces (code) and constraints.
9.7. Appendix G – Documented code for test drivers and stubs.
9.8. Appendix H – Diary of meetings
- References
This project aims to provide a mobile app that supports social hangout activities on campus. In the following, I will make an initial planning on how the project will proceed, and discuss what capabilities and requirements that the app should possess and what responsibilities that I will take to finish this senior project” This I why I do what I love to do”.
Chapter 1: Introduction
This chapter will introduce the purpose and scope of the Social Campus Hangout system, its problem, scope and development methodology, as well as what to expect throughout this document. The last part of this chapter will explain key terms and nomenclature known to the iOS paradigm.
Section 1.1: Problem definition
At FIU, there are several events occurring everyday each semester. Often times many students do not become aware of these events because they do not have a reliable system to effectively relay them. The problematic situation above, leads students to not participate at college events such as companies’ presentations for future internships, sports events, group and student event hangouts, and student meetings.
This lack of information makes it more difficult for students to participate and experience many aspects of the college life.
Section 1.2: Scope of System
The system is build for iOS devices, such iPhones or iPods, and a backend server. Users interact with the iOS devices, which has several layers of technology to parse and receive the users’ and server’s input, and properly configure the information to be sent and displayed. This system will be available only to those within the United States at FIU campus.
Section 1.3: Development Methodology
Figure 1: Unified Software Process Model
Section 1.4: Definitions, Acronyms, and Abbreviations
Acronyms that may be encountered in this document are as followed:
- API Application Program Interface
- SDK Software Development Kit
- GUI Graphic User Interface
- iOS iPhone/iPad Operating System
Section 1.5: Overview of Document
The three phases that went into the development of the Social Campus Hangout system: the software requirements, system design, and testing phases.
The following chapters scrutinize other similar current systems. The third chapter will get into the work distribution in the planning and development of the Social Campus Hangout system, as well as the hardware and software required for its realization. The second part of this deliverable covers the design of the system. Chapter 5 will describe the system architecture and the overall system design. The following chapter will describe the object design. Finally, the last part of this deliverable will cover the testing that was done to the system; system tests, subsystems tests, evaluation of tests. This chapter will also reveal the testing tools that were used during this phase.
Chapter 2: Feasibility Study
Section 2.1: Description of Current System
The current system is the regular email service from FIU, which is our panther mail. This system is good only for slow communication and it doesn’t have an easy way to filter the information that students are or not interested in.
Students don’t always read all of their emails, and often times when they do, particularly event emails, it is too late for them to attend said events. Another disadvantage of the email system is that it is not instantaneous and it does not remind students of the exact moment of the event’s date unless you physically look into the email and read the entire thing.
Section 2.2: Description of Alternative Solutions
One alternative solution is to use other social networks such us Facebook that allows to crated events and is a reliable social network.
FOR FULL DELIVERABLE PROJECT PLEASE DOWNLOAD HERE SocialCampusHangout
Cesar Vega 