Design And Implementation Of A Student Chat Information System

CHAPTER THREE SYSTEM ANALYSIS AND DESIGN
3.1    Adopted Methodology: This student chat information system will make use of Object Oriented Analysis and Design Methodology. This methodology follows the system development life cycle (SDLC), the software lifecycle is typically divided into stages going from abstract  descriptions of the problem to designs then code, testing and finally to deployment.

Figure 2: Object Oriented Life Cycle (Omar, 2015).
3.2    Object-Oriented Analysis: It is the procedure of identifying software specifications in terms of a software system’s object model, which comprises of interacting objects. The earliest stages of this process are analysis (requirements) and design. The distinction between analysis and design is often
described as ‘’what vs. how”. The requirements are:
a.    Elicit Requirements: Define what  the software  needs to do  and the problem it is trying to solve.
b.    Specify Requirements: Describe the requirements, using use cases or user
c.    Conceptual Model: Identify the important objects, refine them, define their relationships and behaviours then finally draw them in a simple diagram.
The primary tasks in object- oriented analysis are:
a.    Identifying the objects.
b.    Organizing the objects by creating object model diagram.
c.    Defining the internals of the objects, or object attributes.
d.    Defining the behaviour of the objects.
e.    Describing how the objects interact.
3.2.1    Object-Oriented Design: It involves implementation of the conceptual model produced during object-oriented analysis. In the object-oriented design, concepts in the analysis model, which are technology-independent, are mapped onto implementing classes, constraints are identified and interfaces are designed resulting in a model for the solution domain. The input for object-oriented
design is provided by the output of object-oriented analysis. But, analysis and design may occur in parallel and the results of one activity can be used by the other.
The implementation details generally include:
i.    Restructuring the class data (if necessary).
ii.    Implementation    of    methods    that    is;    internal    data    structures    and algorithms.
iii.    Implementation of control and of associations.
Goals of Object-Oriented Design
i.    Describe the classes and their relationships using class diagrams (a visual representation of classes needed).
ii.    Describe the interaction between the objects using sequence diagram.
iii.    Apply software design principles and design patterns.
3.3    Analysis of the Existing System
The    existing    system    involves    on-campus    classroom    meetings    for delivering    course    information    and    facilitating    student    conversation    and announcements, where by the physical presence of the lecturer is required at all times and students receive information passively. It also relies on hands–on materials.
3.4    Problems of the existing system
The systems due to some faults detected are:
1.    Late submission of assessment.
2.    Poor Circulation of adequate information.
3.    Fair relationship between lecturers and students.
3.5    Justification of the proposed System
The proposed system is an interactive project that allows communication in real time; it is comprehensive enough, timely and accurate. It has an interface that will help students to share ideas, understand more, and discover abilities that satisfies their personal attributes. It will also have an interface that enables students submit assignments depending on the time duration that is being given by the instructor and get current update about their various courses at any time.
This will speed up the operation because both students and the lecturer can access information at the touch of a button without having to meet face to face but rather communicate real time.
3.5.1 Proposed System Analysis
The proposed system is a web-based system for long lasting solution to the problems of the existing system. Logging here you can have access to the portal, there are drop down menus which includes the students and lecturer section. All these functions are to make it easy for the lecturers and students to access the information system.
3.6    The Analysis Model
The analysis model focuses on structuring and formalizing the requirements of the system. It contains three models: functional, Object and dynamic models. The functional model can be described by the use diagrams. Class diagrams describe the object model. Dynamic model can be described in terms of the
activity diagrams. This system consists following participants:
i.    Lecturer: This participant  updates  or  deletes  new  courses  only  the materials he or she can uploaded.
ii.    Students: This  participant  learns  various  courses  in  the  underlying database.