Systems Analysis Designs - Case Study Example

Running Head: SYSTEMS ANALYSIS DESIGNS NAME: COURSE: INSTRUCTOR: DATE: In this system, webpage will be log in by the students. The owners can update the apartment information as well as, be able to generate statistical reports on demographics and room availability for later reference. Online users can edit the apartment room options by having different selections. These can only be done on the Website. Critical Use Cases Figure 1 Critical Use Cases 3.3.1 Use Case: System Login Requirements Purpose: The purpose of this part of the application is to enable user authentication. A valid account must be used because apartments are for current students and faculty/staff only. Input: The user will be logging in with two inputs (password and username) through the keyboard. Processing: The user inputs will be validated and authenticated against the Computing and Network Services (CNS) Server. The system will check the user name and password to see if they match the data stored onto their database. If the user name or password is not correct, the error message will be portrayed and the user will be requested to re-enter user password and user. If the user is classified as a student, he/she can browse the website, search for available apartments, apply for, and cancel an apartment reservation online. If the user is classified as an owner, he/she will be redirected to an administrator/staff page wherein he/she can update the apartment information and generate the reports. 3.3.2 Use Case: Search Apartment Requirements Purpose: The purpose of this part of the application is to check for an available one- or two-bedroom apartment. Input: There will be three categories: Apartment Complex, Floor Location, and Room Preference. Each category will have different options. The Apartment Complex category will have 3 selections: The Floor Location category will have 2 selections: First and Second. The Room Preference will have 4 selections: One-Bedroom Furnished, One-Bedroom Unfurnished, Two-Bedroom Furnished, and Two-Bedroom Unfurnished. The user will choose one option for each category through the keyboard. Processing: The user must be logged in to do apartment searches. The validation will verify that the user has chosen an option for each category. Output: If the user inputs are not valid (i.e. the user did not choose an option for each category), an appropriate error message will be displayed. If the inputs are valid, a message will be displayed affirming the user’s choices along with the appropriate apartment(s) information for the particular search. 3.3.3 Use Case: Make Apartment Reservation Requirements Purpose: The purpose of this part of the application is to reserve for a one- or two-bedroom apartment. Input: The user will enter nine inputs (name, class, complex type, semester, semester year, room type, room preference, room location, name of spouse (if applicable)) through the keyboard. Processing: The user must be logged in to do the apartment applications. The validation will verify that the user has entered valid data onto the different fields. If all inputs are valid, the related reservation data will be saved onto the apartment database. Output: If the user inputs are not valid (i.e. did not enter an input in one of the required fields), an error message will be displayed. Otherwise, a confirmation Web page will be displayed stating whether there is an available apartment or not, and whether the application has been approved or not. 3.3.4 Use Case: Cancel Apartment Reservation Requirements Purpose: The purpose of this part of the application is to cancel an existing apartment reservation. Input: The user will enter a valid apartment confirmation/reservation number through the keyboard. Processing: The user must be logged in to the system to be able to do apartment cancellations. Once the apartment reservation page is displayed, the user will have the option to confirm or undo the apartment cancellation. Output: If the user chose and confirmed to cancel the apartment reservation, the system will respond with the new data view displaying a success message stating that the apartment reservation has been cancelled. Otherwise, the system will respond with the original data view with a message displaying that no changes has been made to the apartment reservation. 3.3.5 Use Case: Update Apartment Information Requirements Purpose: The purpose of this part of the application is to update information related to the apartment. Input: A staff will select the apartment number through the keyboard. Processing: The staff/administrator must be logged in to do the apartment information updates. Once he/she selected the apartment number, he/she will click on the ‘Search’ button to search for the apartment. The system will check if the inputs are valid and are correct in format. Output: If the inputs are valid and are correct in format, the appropriate apartment information will be displayed and will be ready for editing. The new information entered will be saved onto the database by clicking on the ‘Update’ button and the confirmation Web page will be displayed. Otherwise, an appropriate error message will be displayed. 3.3.6 Use Case: Generate Report Requirements Purpose: The purpose of this part of the application is to provide statistical reports on apartment availability. Input: The user must select the Apartment and enter a valid date for the report to be generated. The apartment availability report will display how many apartments are available in each Apartment Complex to date. Processing: The staff/administrator must be logged in into the system generate the reports. The user inputs will be validated at the client side. If a user has chosen an option, the system will render a statistical report on a single Web page. Output: If user inputs are valid, a Web page containing the statistical report will be displayed. Otherwise, an appropriate error message will be displayed asking the user to choose an option from the category and enter a valid date. Class Description and Diagrams Class Diagram User . User Class Component Diagram Attributes and methods: m_eID: The user’s electronic ID m_password: The user’s password User(): The constructor for user class verifyLogin(): Responsible for authenticating and authorizing the user to use the secure sites isValideID(): Responsible for checking that the eID is correct getUser(): Responsible for getting the user information The other methods are the getters and setters for these variables Student It inherits User class responsibilities. Student Class Component Diagram Attributes and methods: m_SSN: The student’s social security number m_fName: The student’s first name m_MI: The student’s middle initial m_lName: The student’s last name m_birthDate: The student’s birth date m_education: The student’s educational status m_department: The student’s department m_gradDate: The student’s anticipated graduation date m_email: The student’s email address m_address: The student’s street address m_city: The student’s city m_state: The student’s state m_zip: The student’s zip code m_phone: The student’s phone number m_category: The student’s civil status m_sClass: The student’s class Student(): The constructor for student class The other methods are the getters and setters for these variables Dependent This class is instantiated by the Student class. A student may have at most three dependents: one spouse and maximum of two kids only. Dependent Class Component Diagram Attributes and methods: m_sFName: The spouse’s first name m_sMI: The spouse’s middle initial m_sLName: The spouse’s last name m_sSSN: The spouse’s social security number m_sBirthdate: The spouse’s birth date m_sEducation: The spouse’s educational status m_sDepartment: The spouse’s department m_marriageDate: The date of marriage m_c1name: The child1’s name m_c1Birthdate: The child1’s birth date m_c2name: The child2’s name m_c2Birthdate: The child2’s birth date Dependent(): The constructor for dependent class The other methods are the getters and setters for these variables Roommate This class is instantiated by the Student class. A student may have at most 2 roommates. Roommate Class Component Diagram Attributes and methods: m_r1SSN: The roommate1’s social security number m_r1fName: The roommate1’s first name m_r1lName: The roommate1’s last name m_r2SSN: The roommate2’s social security number m_r2fName: The roommate2’s first name m_r2lName: The roommate2’s last name Roommate(): The constructor for roommate class The other methods are the getters and setters for these variables Administrator This class will handle the administrator actions. Administrator Class Component Diagram Attributes and methods: m_eID: The administrator’s KSU electronic ID m_password: The administrator’s password m_adminFName: The administrator’s first name m_adminLName: The administrator’s last name m_adminEmail: The administrator’s email address Administrator(): The constructor for administrator class verifyLogin(): Responsible for authenticating and authorizing the user to use the secure sites generateReport(): Responsible for generating an occupancy report for the apartments The other methods are the getters and setters for these variables Database This class represents the database class. It has all the public methods for querying the apartment database. Database Class Component Diagram ApartmentComplex This class represents an Apartment Complex Apartment Complex Component Diagram Attributes and methods: m_aptName: The apartment complex name ApartmentComplex(): The constructor for apartment complex class isValidAptComplex(): Responsible for checking that the apartment complex is correct getAptComplex(): Responsible for getting the apartment complex information numberOfApt(): Responsible for getting the total number of apartments in an apartment complex The other method is for the getter and setter of the variable Apartment This class represents an apartment in the Apartment Complex Apartment Class Component Diagram Attributes and methods: m_aptNo: The apartment number m_aptComplex: The apartment complex name m_room: The room type of the apartment m_floor: The floor location of the apartment m_price: The price of the apartment m_status: The status of the apartment Apartment(): The constructor for apartment class findApt(): Responsible for searching an available apartment getApartment(): Responsible for getting the apartment information updateApt(): Responsible updating the apartment information Reservation This class is responsible for all apartment reservations. Reservation Class Component Diagram Attributes and methods: m_reservationNumber: The reservation number m_eID: The user’s electronic ID m_aptNo: The apartment number m_aptComplex: The apartment complex name m_semester: The semester in which the reservation is made for m_year: The year in which the reservation is made for m_resvDate: The reservation date m_aptPrice: The price of the apartment m_totalCost: The total cost of the reservation Reservation(): The constructor for reservation class makeReservation(): Responsible for creating a new apartment reservation getReservation(): Responsible for getting the reservation information cancelReservation(): Responsible for canceling an existing apartment reservation The other methods are the getters and setters for these variables ReservationCollection This class serves as a collection class for all reservations. ReservationCollection Class Component Diagram Methods: makeReservation(): Responsible for creating a new apartment reservation getReservation(): Responsible for getting the reservation information cancelReservation(): Responsible for canceling an existing apartment reservation Sequence Diagrams The following sequence diagrams show the core functions of the apartments that will be performed. System Login System Login Sequence Diagram The students will be entering the password and the username to log in to the system to access secure sites. The user will enter his/her eID and password then clicks on the login button on the Login.aspx Web form. The User class will validate the eID and password against the database. If the eID and password are correct, the system will direct the user to an appropriate Web page. Otherwise, the system will prompt the user to check the eID and password. Search an Available Apartment Figure above Search Apartment Sequence Diagram The sequence diagram shows a user has already logged in and has successfully searched an available apartment. The user will select options from three categories: Apartment Complex, Floor Location, and Room Preference on the Search.aspx Web form. He/she will then press the search button. It sends a find apartment message to Apartment then that class sends a query to the database to find the particular apartment being searched. If the result set is not null, the available apartments will be displayed on the same Web form. Otherwise, if the result set is null, the system will prompt an appropriate error message to the user. However, the Web page that will be used is SearchApt.aspx. Make Apartment Reservation Make Apartment Reservation Sequence Diagram The sequence diagram shows a successful apartment reservation made by a user that has logged in. The user will enter required information such as apartment information details and personal information on the Apply.aspx Web form. When the user presses the “Submit” button, a new instance of the Reservation will me made along with the creation of a new reservation number. Then, a makeReservation message will be called in the Reservation class, which then sends a query message to the database. The related reservation data will be saved into the database and the reservation confirmation (ConfirmApply.aspx) Web page will be displayed. Cancel Apartment Reservation The sequence diagram shows a user has already logged in and has successfully cancelled of an apartment reservation. The user will select the reservation number on the drop down list provided on the Cancel.aspx Web page, and then he/she will press the retrieve reservation button. It sends a get reservation message to a Reservation then the Reservation class sends a query get reservation to the Database. If the result set of the get reservation message is not null, the valid reservation information will be displayed on the same Web page ready for cancellation. When the user presses the cancel button, it sends a cancel reservation message to a Reservation then the Reservation class sends a query cancel reservation massage to the Database. If the reservation was canceled successfully, the system will prompt a confirmation message. Otherwise, an appropriate error message will be displayed to the user and no changes will occur in the apartment reservation. The same process will be used when an administrator cancels an existing apartment reservation. However, the Web page that will be used is CancelApt.aspx. Task Breakdown Inception Phase The inception phase will be focused on defining the project requirements. This phase will involve the creation of a vision document detailing the project overview and the critical project requirements. A project plan will also be developed in this phase. It will fully demonstrate the work that needs to be finished in each phase as well as the addition of an estimate of the workload of the task that will form a schedule for the completion of all task activities. A software quality assurance plan will also be utilized, which will describe the required documentation, standards, and conventions needed to ensure product quality. This phase will be marked as ‘completed’ once the committee members approve all the required documentation as well as, the first prototype presented during the first presentation. Elaboration Phase The producer will always demonstrate another executable prototype to demonstrate more and functionality and product features The conclusion of this phase will depend upon the approval of the required documentation and the second prototype given by the supervisory committee after the second presentation. Production Phase The production phase cab be concentrated on the new ideas and testing of the system. It is in this phase that the developer will construct the code and ensure that it is well documented. The code will entirely be tested to guarantee that all necessities are met. This phase will be completed once the committee members approve all required documentation as well as, the final version of the software product after the third and last presentation. The Gantt chart below provides a schedule for completion of the above-defined tasks for each phase. References Alan, D. (2006), Systems Analysis Designs, San tiego: J. Wiley Read More