Limited Offer Get 25% off — use code BESTW25
No AI No Plagiarism On-Time Delivery Free Revisions
Claim Now
Prices start at $5 per page · plagiarism-free papers · free revisions for 14 days 24/7 support: support@bestwriters.com
Uncategorized

System Development and Modern Database Practice

  • Posted
  • Authoradmin
  • Length2,151 words
  • Reading time10 min
Write My Assignment FREE

Assignment 2: Student Information Kiosk (SIK) Case Study – Group Assignment

Student Name

System Development and Modern Database Practice – CIS020-2

Professor Name

University Name

May 23, 2020

Student Information Kiosk (SIK) Case Study

Work Plan

For the development of SIK (Student Information Kiosk) system for the university project team follows a plan (schedule) of work that holds number of phases with different sub-activities or tasks within each work package. The project’s entire work plan is demonstrated in the form of a project plan below in the table and Gantt chart view of the whole plan of work required to achieve the SIK development.

Table 1: Work of Plan

WBSTask NameDurationStartFinish
1Phase One2 daysMon 5/4/20Tue 5/5/20
1.1Initiation2 daysMon 5/4/20Tue 5/5/20
1.1.1Brainstorm Activities0.5 daysMon 5/4/20Mon 5/4/20
1.1.2Initial Investigation0.5 daysMon 5/4/20Mon 5/4/20
1.1.3Prepare Initiation Document0.5 daysTue 5/5/20Tue 5/5/20
1.1.4Research Completed0 daysTue 5/5/20Tue 5/5/20
2Phase Two6 daysTue 5/5/20Tue 5/12/20
2.1Planning6 daysTue 5/5/20Tue 5/12/20
2.1.1Outline system scope1 dayTue 5/5/20Tue 5/5/20
2.1.2User and system requirements0.5 daysWed 5/6/20Wed 5/6/20
2.1.3Identification of Clients, Users and Audience0.5 daysWed 5/6/20Wed 5/6/20
2.1.4Requirement Analysis0.5 daysThu 5/7/20Thu 5/7/20
2.1.5Client Meeting and Interviews0.5 daysThu 5/7/20Thu 5/7/20
2.1.6User Interface Design Plan0.5 daysFri 5/8/20Fri 5/8/20
2.1.7Choose Web Technology to Incorporate0.5 daysFri 5/8/20Fri 5/8/20
2.1.8Gather information on web design elements0.5 daysMon 5/11/20Mon 5/11/20
2.1.9Plan System Modules0.5 daysMon 5/11/20Mon 5/11/20
2.1.10Finance Management Plan0.5 daysTue 5/12/20Tue 5/12/20
2.1.11Risk Management Plan0.5 daysTue 5/12/20Tue 5/12/20
2.1.12Gain Approval Meeting0 daysTue 5/12/20Tue 5/12/20
2.1.13System Planning Accomplished0 daysTue 5/12/20Tue 5/12/20
3Phase Three4 daysTue 5/12/20Fri 5/15/20
3.1Design4 daysTue 5/12/20Fri 5/15/20
3.1.1UML Modeling and ERD0.5 daysTue 5/12/20Tue 5/12/20
3.1.2Framework Design0.5 daysTue 5/12/20Tue 5/12/20
3.1.3High level system design0.5 daysWed 5/13/20Wed 5/13/20
3.1.4Architecture design0.5 daysWed 5/13/20Wed 5/13/20
3.1.5System mockup representation0.5 daysThu 5/14/20Thu 5/14/20
3.1.6System Review0.5 daysThu 5/14/20Thu 5/14/20
3.1.7System design completed0 daysFri 5/15/20Fri 5/15/20
4Phase Four2 daysFri 5/15/20Sun 5/17/20
4.1Implementation2 daysFri 5/15/20Sun 5/17/20
4.1.1Deploy business template0.5 daysFri 5/15/20Fri 5/15/20
4.1.2Choose and run available theme0.5 daysFri 5/15/20Fri 5/15/20
4.1.3Review elements0.5 daysMon 5/18/20Mon 5/18/20
4.1.4Revisions accomplished0.5 daysMon 5/18/20Mon 5/18/20
4.1.5Finalize look and review0.5 daysTue 5/19/20Tue 5/19/20
4.1.6Implementation Finished0 daysTue 5/19/20Tue 5/19/20
5Phase Five3 daysMon 5/18/20Wed 5/20/20
5.1Testing3 daysMon 5/18/20Wed 5/20/20
5.1.1Testing of each module0.5 daysMon 5/18/20Mon 5/18/20
5.1.2Test each functionality of website0.5 daysMon 5/18/20Mon 5/18/20
5.1.3Integrate modules0.5 daysTue 5/19/20Tue 5/19/20
5.1.4Check system quality0.5 daysTue 5/19/20Tue 5/19/20
5.1.5Document testing plan0.5 daysWed 5/20/20Wed 5/20/20
5.1.6Testing completed0 daysWed 5/20/20Wed 5/20/20
6Phase Six1 dayThu 5/21/20Thu 5/21/20
6.1Closure1 dayThu 5/21/20Thu 5/21/20
6.1.1Report Documentation1 dayThu 5/21/20Thu 5/21/20

Identification of Clients, Users and Service Audience

The proposed touch-based student information kiosk system can be helpful for different kinds of users, clients and serves different purposes for its intended service audience. Each user, client or audience can perform respective task on kiosk interface through the proposed database-centric application. From the case we have recognized the following users, clients and intended audience of the SIK system:

Students: Students within the university campus are the real users of the SIK system that can actually use this system to get access to updated and different types of information about events happening across campus and outside, acquire access to different sources of help and know about student communities within university. Students likewise serve as the primary service audience of this system that can use the computerized one-stop facility at hand and get access to information about workshops, guest lectures, courses, departmental events, student clubs, and other student facilities including sports, gym, shopping, and exclusive offers accessible. These users can access this system to know about their personal details including bank accounts, cultural activity participation etc. These users access one-stop database system that offers up-to-date and detailed info about the university and helps them to search and navigate for different varieties of information.

Admin: This is the root user (on administrative level) that can access the system for updating and handling changes and updates in provided details through kiosk system. The admin can use the SIK system as main user with all rights and permissions to have authority of updating all kinds of datasets.

Guest (visitor): Another user of the SIK system is guest user or visitor who requires using the system for generic information without any login procedure from nearby kiosk system or within campus. Such users only want to know standard details about the individuals.

Staff (Faculty): One more kind of client of the SIK system includes staff or faculty member that can access the SIK system to pick the feedback section for offering feedback to the student within courses and lab assignments[ CITATION Adh17 l 1033 ].

Collecting and Refining the Initial Set of User Requirements

For a project user requirements describe precisely what actions the users can perform with the system. They frequently termed as end-clients are crucial for the system’s success and a substantial amount of time is generally consumed collecting such requirements. Certainly, user requirements might very fine be the utmost significant requirements for a software development group to get exact. As such requirements describe how the end-client is to participate with the system; they outline what the system must perform for the user. In this project, we are planning to build a prototype application eventually aimed for touch screen interface known as Student Information Kiosk (SIK) is a database-based/RDMS-based system that is intended and designed to permit scholars of a university to use a centralized or one-stop and automated/computerized service. The following user requirements are supposed to be collected and refined for the SIK system of the university from students, staffs and visitors as the system’s users:

  1. As a student/staff I want the system to offer updated details regarding all events/programs happening on college campus including sources of help, student nights, guest lectures, clubs, workshops and chosen information related to local services, community, exclusive offers, sports activities, gym, and discounted shopping.
  2. As a student I want the system to incorporate data sources of native facilities including bank account retailers of student, cultural and sports activities so that I can easily search them.
  3. As a student I want the system to keep my personal information and display as soon as I access.
  4. As a student I want the system to provide me a facility to book for an activity or service within university campus.
  5. As a student I want the system to provide me an access to all divisions and list of staff members within each division.
  6. As an admin I want the system to provide me a facility so that I can easily manage information sources of all types within campus.
  7. As an admin I want the system to facilitate me an option so that I can generate students’ report and feedback for changes in information sources.
  8. As a visitor/guest I want the system to offer me an access without login process so that I get general details from kiosk nearby or inside the college campus.
  9. As a student I want the system to enable me to get access to sources of help and information regarding Luton as a group.

Analyzing Requirements with an Appropriate Method

Analyzing the gathered user requirements for the proposed SIK system involves mapping of the system workflow consequently that we can understand, analyze and create mandatory modifications to the process or workflow of the system. There are several requirement analysis methods that can be utilized according to the software or database-centric system creation procedure like BPMN, UML, and others however for this case we use context diagram method for analyzing the elicited requirements from the main users of the SIK system[ CITATION Ken122 l 1033 ]. The context flow illustration evaluates all gathered requirements and could offer a pictorial view of the whole SIK system. Afterward the accomplishment of the analysis, it is anticipated that the project understandability might enhance considerably. After the analysis of these requirements we move further and model these requirements with more than one modeling approaches and notations. The context diagram below in figure 1 is a simple way that outlines the interfaces and boundaries of the projected SIK system with the outside domain and recognizes the entities out of the projected system that collaborate with the SIK system.

Fig. 1 Analysis of Collected Requirements from Users (Student, Admin, Visitor and Staff/Faculty)

Functional and Non-functional Requirements

Functional requirements

  1. The system shall admin user a unique identification number (username) and a unique password exclusive to his account for managing and updating all information sources and datasets and other users’ details.
  2. The system shall offer admin an ability to produce feedback reports of students.
  3. The system shall require student user to enroll/register first with the personal details and then provide with unique username and password for login to the system.
  4. The system shall initially authenticate each kind of user with different access permissions and validate the credentials placed within the back-end database system.
  5. Every visitor/guest user shall be able to navigate and access system for general information without requiring login to the system.
  6. Every student shall able to browse or search various services via category (group-wise) within the system.
  7. The system shall offer student to request and check for availability of service e.g. local service or other.
  8. The system shall offer student to book for an activity/service within the university.
  9. The system shall notify student of their confirmation of service/activity booking via email/message.
  10. The system shall offer student with functionality to update/edit/cancel their booking/event information or their respective personal information on the portal.
  11. The system shall offer admin with an ability to update all information and details of all students, faculty and other users of the system.
  12. The system shall enable user to access system with an appropriate web-based interface screen.
  13. The system shall enable students/faculty to search all informational events including community, university and information sources of support within campus.
  14. The system shall enable staff to provide their feedback of the students on course and lab assignments.
  15. The system shall permit faculty to edit/update feedback accordingly.

Non-functional Requirements

Performance

  • The SIK system should minimalize errors and understandable error notification must be shown that guide client to manage it.
  • Each module and function should execute fine.
  • The system shall be compatible with suitable desktop device/touch screen interface devices with high RAM and processing speed.
  • The system shall respond within 2 seconds of user’s input on the screen[ CITATION Sam17 l 1033 ].

Availability

  • The system shall be accessible to its clients without or with internet connectivity 24X7 as client might have access to the same with the native intranet from inside the university campus.

Usability

  • By instructing clients to turn out to be aware of the system and via designing user-friendly user interface (UI), the end-clients shall be capable of requesting for service information/booking/other information sources.

Reliability

  • The system shall offer consistent results on different inputs of the users accessing different functionalities.
  • The system shall keep backup of information regularly e.g. must backup information each hour within the database.

Security

  • The admin user shall offer great security enabled interface portal for managing different users and safeguard the confidential information of students and university management.
  • The system shall offer external protection via validating the sign-up/login verification and shall provide suitable protection concerning unauthorized data access[ CITATION Sam17 l 1033 ].

System Modelling

The modeling of the SIK system outlines the route from non-functional and functional requirement description to the system design using stepwise transformation and creation of models and drawings. For this purpose, unified modeling language or UML is used that visualizes, specifies, constructs and documents the system requirements. This approach provides a generic method to compose the system’s artifacts comprising conceptual aspects like business procedures, functions, and database elements[ CITATION Aji19 l 1033 ]. We will model the SIK system using two kinds of UML diagrams e.g. class and use case diagram.

UML Class diagram: For modeling the SIK system, we initially develop a class diagram that illustrates different entities (classes) and their attributes (class variables and methods) and the relationships or connections among them with the help of UML notations[ CITATION Dou01 l 1033 ]. In the context, a class signifies an entity or actor within the proposed system and outlines the data variables and methods within an object that is a particular instance within the system. This illustration will further help in modeling the SIK system using object-oriented modeling and further system implementation. Major functional requirements are modeled through this UML class drawing as shown below:

Fig. 2 UML Class diagram

Use Case Diagram: We likewise model SIK system using another UML notation known as use case diagram that encompasses actors act as system users (student, staff, admin & staff) with their respective actions (functions they are obliged to perform with the system).

Fig. 3 Use Case Diagram

Works Cited

Adhoni, Z. A., Ambreen, S., Islam, M. N., & Mohammadi, M. (2017). Developing KIOSKs – Touch Based Interactive Information System. International Journal of Computer Science and Information Security (IJCSIS), 15(10), 166-176.

Kendall, & Kendall. (2012). Systems Analysis and Design. Prentice Hall.

Paradkar, S. (2017). Mastering Non-Functional Requirements. Packt Publishing Ltd.

Rosenberg, D., & Scott, K. (2001). Applying Use Case Driven Object Modeling with UML: An Anotated E-commerce Example. Addison-Wesley Professional.

Singh, A. (2019). Object Oriented Modeling And Design With UML. Ajit Singh.

The post System Development and Modern Database Practice appeared first on My Assignment Online.

Plagiarism Free Assignment Help

Expert Help With This Assignment — On Your Terms

✓ Native UK, USA & Australia writers ✓ Deadline from 3 hours ✓ 100% Plagiarism-Free — Turnitin included ✓ Unlimited free revisions ✓ Free to submit — compare quotes

admin

Academic writer and editor at BestWriters.

Get your paper off your plate tonight

Post your instructions for free. Prices start at $5 per page.

Place an order