ASSESSMENT 2 BRIEF
Subject Code and Title
MIS605 Systems Analysis and Design
The Subject Learning Outcomes demonstrated by successful completion of the task below include:
Based on your responses to Assessment 1 – Written assessment, perform process and data modelling and develop and document a number of design diagrams using UML (including Context Diagram, Level 0 and Level 1 Data Flow Diagram, Entity Relationship Diagram).
In Assessment 1, you performed a comprehensive requirement analysis for the online student enrolment system at the ABC University. With an in-depth understanding of the functional requirements of the System, you are now required to perform further analysis through process and data modelling. In doing so, you also need to provide a preliminary data storage design for the System.
Both process modelling and data modelling can be used to provide deeper understanding of a new System. Thus, they are an integral part of System Analysis. Process modelling describe business processes – i.e. the sequence of activities that people do; while data modelling seeks to describe the data flows through those processes. Data flow diagrams (including context diagrams) and entity relationship diagrams are the most common process and data modelling techniques used in industry.
MIS605_Assessment 2_Additional case information document.
Create and document a Context Diagram for the System. (15 marks)
Create and document a Level 0 Data Flow Diagram (DFD). The Level 0 DFD should contain all the major high-level processes of the System and how these processes are interrelated.
Select three major and non-trivial processes from Level 0 DFD, decompose each of the processes into a more explicit Level 1 DFD.
Using your own experience with similar online student enrolment systems and the information provided in the case study:
Note: the case study has not and does not intend to provide a comprehensive description of entities in the System. You are expected to use your own experience with information systems in general and online student enrolment systems in particular to develop this ERD. For example, would Subject Name be an attribute for a Subject? Would Date of Birth be an attribute for Students?
Should data be stored in files in a file system or in a database for the System? Justify your answer.
Translate the ERD you developed in Task 4 into a physical relational database design. Document database tables and their relationship in MSWord file. Normalise your database design to the Third Normal Form (3NF).
Word Count and Layout
Our online student enrollment system allows students before the start of their semesters to enroll in their subjects. Not only does this enrollment system allow foreign students who are enrolled via the network without commuting to the school, but business regulations are also integrated. These market rules provide a broad variety of procedures and legislation, such as the content provision, the payment status of the student, the judgment of the course coordinator and the communication of the qualifications and experience of students to the expected enrolling subjects. It is one of the key components of the Student Registration System. Here's where the student topic selection choice is added. The outcome foretaste, semester preview and profile functionality are also included in this. The available subject list for the semester will be provided by this interface. It helps the student to select the subjects, a packed GUI therefore. The interface between the student part and the subject is the bridge Ingredient. Despite its possible complex business rules, the key components of the Student Registration System. This is where the selection option is also an interesting system for the college sub-online student enrollment system. The system's notification functionality offers highly automated computer-human contact with the system. Human and computer contact is made easy with SMS, email and web pages. The web page is, in particular, specifically configured to be able to identify the user's browser platform, such as the PDA. The rendering of different file formats is subject to the client requesting it. Finding business rules in XML makes it possible to be portable for the system that hosts the web application and also allows flexibility to modify business rules without modifying programming source codes. In summary, this study conceptually shows the interactivity characteristics of the framework while maintaining the eject of implementation knowledge is implemented.
A context Diagram meaning, also known as a level 0 DFD, offers a broad explanation of an information system and how it communicates with external entities. The student provides which of the selected classes, parts, and lab groups are. To see if the rules and regulations (credit limits, prerequisites and collisions) are applied, the machine tests the course collection. If so, the form for registration is generated and stored. As long as the student does not accept the registration form, the student may make changes to the registration form. Only each repeated courses cannot be withdrawn and the laws and regulations are enforced at all times.
For the current semester, the student gets the services provided as well as the parts of the course. The system obtains the curriculum of students and philtres out the courses that cannot be recorded. The scheme adds repeat courses to the chosen courses that examine the student's academic background. The student delivers the preferred courses and pieces. The method applies the rules and regulations to decide if the registration of the student course meets requirements such as credit limits, prerequisites and collisions. The learner is presented with the approved and rejected courses. If there are any rejected classes, the learner makes new choices. Finally, the student accepts the admission. The device shows a form for registration.
The system presents detailed details for the semester, such as the school year, semester, courses offered and their sections.
The framework philters out certain courses that students do not choose because they are not part of the curriculum or they are not comfortable with their prerequisites. Specifically, repeat courses are illustrated.
The learner makes choices for the course. The repeat courses are applied by the systems directly.
The consultant approves / rejects the entire registration or just any of the courses.
The person makes the course selection improvements.
A course registration form is created by the system.
Level 0 DFD
The data flow diagram of the enrollment as an initiation stage, the scheme is also used to produce a description of the enrollment without going into great detail. Usually, it consists of the complete flow of application data and registration process operations. It includes all user flows and f or data processing visualization and structured registration process and workflow design, their entities, such as all flows, of registration, student, and course, Fees, test, password, and authentication. All of the below diagrams were used.
Zero Level Data Flow Diagram Enrollment Level 0 DFD System:
Level 0 DFD diagram
This is the Enrollment System.com Zero Level DFD where we have built the high-level Enrollment process.
It's a simple description of the entire framework or method of enrollment being studied or modelled.
It is intended to be an identified as high-a-glance view of Examination. Login and Authentication that shows the system as a common high-level method, with its link to Enrollment. Student and Course outside entities. It should be grasped easily by a large audience.
In zero level DFD of the Enrollment System, we identified the high level flow of the Enrollment system, which should be easily understood by a broad audience including Enrollment, Course and Review.
Entities of the High Level and Enrollment Framework Phase Flow:
Managing all the registration
Management of all students Management of all courses Management of all fees
Managing all tests managing all password management
Managing all authentication processes.
Level 1 DFD
The Enrollment System First Level DFD (1st Level) demonstrates how the system is divided into sub-systems (processes) that each address one or more processes. Data flows to or from an external force and contains all the attributes of the entire Enrollment System. It also defines the internal authentication, login, review, fees, course data stores that must be present for the registration system to do its job and shows the stream of activities between the registration system different sections of the system registration, course, username and password, authentication, inspection. An extra comprehensive running away of sections of the 1st altitude DFD is given by DFD Level 1.
Level 1 DFD diagram
The Enrolment Framework Entity model is represented in this ERD. This entity-relationship diagram shows the entire database tables’ visualization tool and the relationships between student, fees, enrollment, login, etc. It used structure data and interfaces of the Enrollment System to describe the relationships between organized data classes. Enrollment, student, course, costs, review and login are the key entities of the Enrollment System.
Course (Course_ID, Student_ID, Course_Registration, Total _Course_name, Course_type, Course_year)
Class(Class_ID, Class_name, Location, Time, Student_ID, Campus_ID)
Student(Student_ID, student_Name, Collage_ID, Email_ID, Password, Address, Enroll_Date, Payment_ID, Course_name)
Campus(Campus_ID, Campus_name, Location, Time, Student_ID, Class_ID)
Subject(Subject_ID, Course_ID, Subject_name, per_Trimester)
Program Director(Program_ID, Program_gen_Report, Course_ID,)
Payment(payment_ID, course_Fee_pay, Total)
The registration details are stored in the registration tables for all tables.
The primary key and unique keys are included in each entity (login, course, test, student, and enrollment).
The Entity Course, Examination Binding, Student Entities with International Key, Enrollment
One-to-one and one-to-many relationships including test, fees, login, and registration are possible.
All registration, review, course and login entities are standardized and duplicate records are reduced.
For quick query execution, we have implemented encoding on each Enrollment Column tables.
A Database Management System is a software function with the aim of enable users to identify, build , maintain and share databases efficiently. To define a database, the data types, structures and constraints of the data to be store in the list are specified. Create a record requires store the information on some DBMS-controlled storage medium. Maintaining a database requires updating the database whenever appropriate to adapt and represent changes in the mini-world and evaluating results for each update. Sharing a database means allowing access to the database by several users. DBMS also functions as an interface between the database and the systems of the end users or application. It provides data access control and maintains that information is reliable and accurate by specifying rules for it.
Through submitting questions or requests for data to the DBMS, an application programmer accesses the database. A query causes the database to retrieve some data. The effectiveness of any institution, such as the Department of center at the university of algeria, depends on the ability of any entire organisation, such as the Department of institute at the university of algeria, to collect accurate and timely data on its activities, to track such data efficiently and to use it to interpret and guide its activities. The integrated student database system (Student, Registrar, HOD) offers multi-source data to users with a single view. In order to produce a completely reliable number for any individual represented in these data sources , data fusion is concerned with resolving the inconsistency of data present in heterogeneous data. The framework developed is the development of a structured and functional integrated student database system that will maintain and store student records. This easy-to-use, integrated database programme aims at reducing resources required on routine duties.
The structure is intended to recognize the process and generate reports correctly, and any person can select the services at any time when there are internet facilities available. The system is also designed to deliver better services to consumers, deliver accurate, valid and reliable knowledge and documents, and ultimately improve efficiency by transforming physical processes into electronic form. The platform was developed using technologies like PHP, HTML, CSS and MySQL. PHP, HTML and CSS are used to construct the user interface and the database is generated using MySQL. The system is free of errors and very successful and less time-consuming, according to the care taken to develop it. All the phases of the software development cycle are used and it is worth stating that the structure is very consistent. Allowance is made for future development within the system.
'SELECT STUDENT NAME, STUDENT ADDRESS, PROGRAMME REGISTERED' is an expression that specifies the fields or data items to be used in the answer. "FROM STUDENT" tells the system what column to look at, and "WHERE PROGRAMME REGISTERED= COMP" places a search philtre, removing all information from education records registered in programmers other than COMP from the database. By supplying a point and click interface to create the query, some graphical systems generate SQL for the user. Graphical languages and SQL are non-procedural programming, which means that, as a procedural programming language like COBOL would entail, they include asking the machine what is required, rather than how to do the query. Languages and graphical interfaces of the fourth generation include tools that, depending on the complexity of the problem and the abilities of the user, can be used by skilled users or programmers. In order to perform the same queries, both fourth-generation languages such as SQL and graphical database interfaces make it much simpler to query the database than using a procedural software package.
The tables must be constructed in such a way as to prevent the use of duplicate non-key items in order for relational databases to function properly with multiple tables, and also to ensure that all non-key items are completely associated with the relevant key(s). This method is called normalisation of data and is usually implemented in steps, usually stopping after three. 1NF (First Normal Form), 2NF (Second Normal Form), and 3NF (Third Normal Form) are defined as these phases of normalisation.
One or more attributes (also known as an instance or, in terms of the table, a row) make up a specific 'key' for the record. It is called a blended or comma separated key if the key is a combination of two or more attributes. Keys from other tables are typically the components of a concatenated key, and each part of the concatenated key often acts as a connexion to the attribute image. As international keys, the components of a concatenated key from other tables are referred to. Multiple tables are used in the student / course database to handle the details concerning student enrollment in courses. One table, for example , includes data on students. The second table includes data on the available courses, while the third table illustrates the relationship between the two other entities, resulting in a third entity.
Subject_Course (Course_ID, * Subject_ID)
Program Director(Program_ID,Campus_ID, Course_ID,)
In short, the backend engine of the enrollment architecture is related to the business rules the front-end engine operates to include high satisfaction for the user interface. The system is capable of completing the student enrollment process from the course registration form to the implemented in an effort process, with the technical and business interface, normal path to the communication capability. The enrollment workflow allows the student and the SA to display the details in the support year’s cycle in two proportions. Students insert registration information into the system and can alter the information within a certain amount of time. Business registration rules, such as pre-requisites, timetables, administrative criteria and criteria for graduation, are stored in XML. Along with its development setting, this format facilitates the portability of business rule files on different platforms. Another important reason that uses XML is to make it possible for SA to modify business process from periodically without modifying the programming source code.