Virtual University Project

Final Project Ideas (CS619)

Virtual University Projects

CS619-Viva Exam Preparation Basic Question File Solved By Arslan

vu all projects 2023-24

Catering Support Service Company (project)

(SRS document for your SRS practice)

Assignment no 1

1.Software Requirements Specification

Table of Contents
1.Scope (of the project)                                                                                                            
2.Functional Requirements Non Functional requirements                                
3.Use Case Diagram                                                                                         
4.Usage Scenarios                                                                                 
 1.Scope of Project:
The main aim of this project is to provide a better system to the sites to handle all their daily stock related activities digitally. So, that the stock can be managed at the individual sites and the performance of the sites can be monitored and can be audited as well. Also To produce a simple, yet suitably effective user friendly interface and a system that is easily maintainable, efficient and practical.
2. Functional Requirements:

•  The system will allow the administrator to add/edit/delete area offices.
• The system will allow the administrator to add/edit/delete supervisor for each area.
• The system will allow the administrator to add/edit/delete auditor which can audit the all operation of every area.
• The system will allow the administrator to add/edit/delete accountant which can audit the all operation of every area.
• The system will allow the store keeper to add/edit/delete items.
• The system will allow the store keeper to issue items according to advice of operation manager.
• The system will allow the store keeper to issue items.
• Storekeeper can check all the balance of its items.
• Storekeeper will receive requests from operation manager.
• The system will allow the supervisor to check orders.
• The system will allow the supervisor to check payments of orders.
• The system will allow the supervisor to allot the projects.
• The supervisors will add/edit/delete the worker.
• The system will allow to add/edit/delete the project managers.
• The system will allow to add/edit/delete the operations manager.
• The system will allow operations manager to allot manpower.
• Operations manager will allot required items.
• The operations manager will view orders.
• The operations manager can make requests to store keeper.
• The general auditor can check the all orders.
• The general auditor can check consumption records of all items (food, non-food, assets).
• The general auditor can check the all payments by the customers.
• The general auditor can check the balance sheets.
• The general auditor can mark on projects.
• The customer can make orders.
• The customer selects occasion type, menu, date and time of the party/occasion.
• The customer can check the order status.
• The customer will be issued a voucher for payment.

 Non Functional Requirements:

•  The system will be easy to use (user friendly).
• The system will use less data and space.
• Data entry and search data entry.
• Information retrieval will be fast.
• Less manpower will be required when system will be deployed.
• All the operations will be accurate and accountable.
• Data of all projects can be imported and exported.
• System should be capable of supporting multiple users without affecting its performance.

 3.Use Case Diagram(s):
  (FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
  4.Usage Scenarios:
 (FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )

Failure: The database contents will remain unchanged.Main Success ScenarioThe administrator will login first.
The administrator will enter the all data about the office.
The system will validate the information.
A message will be displayed.
Use case ends.Alternative ScenarioIf administrator doesn’t want to save the records then he press the cancel button. The record is not saved in the database and use case is ended.Exception The system will generate exception if the data is incorrect or data is already is present in the database.

Failure: The database contents will remain unchanged.Main Success ScenarioThe administrator will login first.
The administrator will enter the all data about the supervisor.
The system will validate the information.
A message will be displayed.
Use case ends.Alternative ScenarioIf administrator doesn’t want to save the records then he press the cancel button. The record is not saved in the database and use case is ended.Exception The system will generate exception if the data is incorrect or data is already is present in the database.

Failure: The database contents will remain unchanged.Main Success ScenarioThe administrator will login first.
The administrator will enter the all data about the office.
The system will validate the information.
A message will be displayed.
Use case ends.Alternative ScenarioIf administrator doesn’t want to save the records then he press the cancel button. The record is not saved in the database and use case is ended.Exception The system will generate exception if the data is incorrect or data is already is present in the database.

Failure: The database contents will remain unchanged.Main Success ScenarioThe administrator will login first.
The administrator will enter the all data about the office.
The system will validate the information.
A message will be displayed.
Use case ends.Alternative ScenarioIf administrator doesn’t want to save the records then he press the cancel button. The record is not saved in the database and use case is ended.Exception The system will generate exception if the data is incorrect or data is already is present in the database.

Failure: The database contents will remain unchanged.Main Success ScenarioThe customer visits the page.
Enter all the information about the order.
Enter his bio data.
Presses the order button.Alternative ScenarioIf customer doesn’t want to make order then he presses the cancel button and leaves the page.ExceptionThe system will generate exception if the data is incorrect or data is already is present in the database.

SRS-Document

For more detail about SRS and Virtual University Projects Click Here… 

Final Project Ideas (CS619)

Virtual University Projects

Mobi Quiz (Assignment no 2)

Methodology and Work Plan

Table of contents

1. Introduction of the Planning Phase
2. Methodologies

2.1 Existing Methodologies
2.2 Adopted Methodology
2.3 Reasons for choosing the Methodology

3. Work Plan

1. Introduction of the planning phase:
The important task in creating a software product is extracting the requirements or requirements analysis. Customers typically have an abstract idea of what they want as an end result, but not what software should do. Incomplete, ambiguous, or even contradictory requirements should be recognized at this point. Frequently demonstrating live code may help reduce the risk that the requirements are incorrect.
Project planning is part of project management, which relates to the use of schedules such as Gantt charts to plan and subsequently report progress within the project environment. Initially, the project scope is defined and the appropriate methods for completing the project are determined.
Once the general requirements are gleaned from the client, an analysis of the scope of the development should be determined and clearly stated. Certain functionality may be out of scope of the project as a function of cost or as a result of unclear requirements at the start of development.
If the development is done externally, this document can be considered a legal document so that if there are ever disputes, any ambiguity of what was promised to the client can be clarified.
Advantages:
It involves creating of a set of plans to help guide your team through the execution and closure phases of the project. The plans created during this phase will help you to manage time, cost, quality, change, risk and issues.

2. Methodologies:

 The Software Development Life Cycle is a process of creating or altering information systems, and methodologies that people use to develop these systems.
Methodology is generally a guideline for solving a problem, with specific components such as phases, tasks, methods, techniques and tools
2.1 Existing Methodologies:
There are a number of methodologies that are used in today’s computer life according to the project. The existing methodologies are as below:
2.1.1  Waterfall Model:
Description:
All projects can be managed better when segmented into a hierarchy of chunks such as phases, stages, activities, tasks and steps.  In system development projects, the simplest rendition of this is called the Waterfall methodology.
In the traditional waterfall methodology, first comes the analysis phase, then the design phase, followed by the implementation phase, with testing completing the process. The team that does each phase is different and there may be a management decision point at each phase transition.
The waterfall provides an orderly sequence of development steps and helps ensure the adequacy of documentation and design reviews to ensure the quality, reliability, and maintainability of the developed software.
The Waterfall Model is a documentation-driven model. It therefore generates complete and comprehensive documentation and hence makes the maintenance task much easier.
It however suffers from the fact that the client feedback is received when the product is finally delivered and hence any errors in the requirement specification are not discovered until the product is sent to the client after completion. This therefore has major time and cost related consequences.
The graphical representation of this model is following:
(Download attachment file below for model)

Advantages: 

•  It is a linear model and the linear models are the most simple to be implemented.
• Waterfall model provides a template into which methods for analysis, design, coding, testing and support can be placed
• It remains a widely used procedural model for software engineering.
• The amount of resources required to implement this model is very minimal.
• One great advantage of the waterfall model is that documentation is produced at every stage of the waterfall model development. This makes the understanding of the product designing procedure simpler.
• After every major stage of software coding, testing is done to check the correct running of the code.

Disadvantages: 

•  Real project rarely follow the sequential flow that the model proposes. Although the waterfall model can accommodate iteration, it does so indirectly. As a result, change can cause confusion as the project team proceeds.
• The waterfall model requires all requirements explicitly, but it is often difficult for the customer to state all requirements explicitly.
• A working version of the program will not be available until late in the project time-span.
• The greatest disadvantage of the waterfall model is that until the final stage of the development cycle is complete, a working model of the software does not lie in the hands of the client.

2.1.2  Rapid Application Development Model:
Rapid application development is a software development methodology, which involves iterative development and the construction of prototypes. It is a merger of various structured techniques, especially the data driven Information Engineering with prototyping techniques to accelerate software systems development.
It is a high speed adaptation of the linear sequential model in which fully functional system in a very short time (2-3 months). This model is only applicable in the projects where requirements are well understood and project scope is constrained. Because of this reason it is used primarily for information systems.
2.1.2.1 Spiral Model:
 Description:
This model was developed by Barry Boehm. The main idea of this model is to avert risk as there is always an element of risk in development of software. In its simplified form, the Spiral Model is Waterfall model plus risk analysis.
In this case each stage is preceded by identification of alternatives and risk analysis and is then followed by evaluation and planning for the next phase. If risks cannot be resolved, project is immediately terminated.
As waterfall methodology offers an orderly structure for software development, demands for reduced time-to-market make its series steps inappropriate. The next evolutionary step from the waterfall is where the various steps are staged for multiple deliveries or handoffs.
The ultimate evolution from the waterfall is the spiral, taking advantage of the fact that development projects work best when they are both incremental and iterative, where the team is able to start small and benefit from enlightened trial and error along the way.
A graphical representation of the spiral model is following:
(Download attachment file below for model)
Advantages:

•  Risk reduction mechanisms are in place.
• Supports iteration and reflects real-world practices.
• Systematic approach
• Estimates (budget, schedule, etc.) become more realistic as work progresses, because important issues are discovered earlier.
• It is more able to cope with the changes that software development generally entails.
• Software engineers can get their hands in and start working on a project earlier.
• Disadvantage:

Requires expertise in risk evaluation and reduction, Complex, relatively difficult to follow strictly:

• Applicable only for large systems.
• Highly customized limiting re-usability.
• Applied differently for each application.
• Risk of not meeting budget or schedule.
• Risk of not meeting budget or schedule.

2.1.3  Object oriented Methodology:
Object-oriented lifecycle models appreciate the need for iteration within and between phases. There are a number of these models. All of these models incorporate some form of iteration, parallelism, and incremental development.
2.1.3.1 Extreme programming Model:
 Description:
Extreme Programming is the best known iterative process. In extreme programming, the phases are carried out in extremely small steps compared to the older batch processes.
The first pass through the steps might take a day or a week, rather than the months or years of each complete step in the Waterfall model.
The graphical representation is following:………………………………
(Download attachment file below for graph)
Advantages:
Extreme Programming has different key advantages for different audiences.

• For developers, XP allows to focus on coding and avoid needless paperwork and meetings. It provides a more social atmosphere, more opportunities to learn new skills, and a chance to go home at a decent time each night.
• For the Customer, XP creates working software faster, and that software tends to have very few defects.

• For management, XP delivers working software for less money, and the software is more likely to do what the end users actually want.

Disadvantages:
Disadvantages of the XP are followings:

• The biggest disadvantage of Extreme Programming is hard to do. It’s difficult to get many developers to accept the practices, and it takes a lot of discipline to keep doing them all.
• Customers may not like the idea of having to be so involved. Management may have trouble adapting to a process that, itself, adapts to the changing needs of the business.

• Certain people may feel their jobs are being threatened, particularly architects, testers, and project managers.

 2.1.4 Rapid Prototyping Model:
The Rapid Prototyping Model is used to overcome issues related to understanding and capturing of user requirements. In this model a mock-up application is created rapidly to solicit feedback from the user.
Once the user requirements are captured in the prototype to the satisfaction of the user, a proper requirement specification document is developed and the product is developed from scratch.
2.1.4.1 Incremental model:
Description:
Various methods are acceptable for combining linear and iterative systems development methodologies, with the primary objective of each being to reduce inherent project risk by breaking a project into smaller segments and providing more ease-of-change during the development process.
A series of mini-Waterfalls are performed, where all phases of the Waterfall development model are completed for a small part of the systems, before proceeding to the next incremental.
The graphical representation of the incremental model is following:…………………………….
(Download attachment file below for graph)
Advantages:

• Generates working software quickly and early during the software life cycle.
• More flexible, less costly to change scope and requirements.
• Easier to test and debug during a smaller iteration.
• Easier to manage risk because risky pieces are identified and handled during its iteration.
• Iterations are easily managed milestone.

Disadvantages:

•  Each phase of an iteration is rigid and do not overlap each other.
• Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle.

2.2 Adopted Methodology:
 The adopted methodology for this project is VU Process Model which is a combination of waterfall and spiral models.
The graphical representation of VU Process Model is following:…………
(Download attachment file below for model)

2.3 Reasons for choosing the Methodology
There are several reasons for adopted methodology for this project.
Salient features of waterfall are given below:

• It is the formal method.
• It is type of top-down development.
• It is composed of independent phases to be done sequentially.
• In it resources can be held constant but the system size grows.
• The spiral size corresponds to system size, while the distance between the coils of the spiral indicates resources.

Methodology and Work Plan

Final Project Ideas (CS619)

Virtual University Projects

Mobi Quiz (Assignment no 3)

Design Document 1

Table of Content    (Virtual University Projects)

1. Introduction (of analysis and design phase)
2. Overview (of proposed system)
3. Data Flow Diagrams (DFD)
   (To be developed using Microsoft Visio)
4. Entity Relationship Diagram (ERD)

(To be developed using Microsoft Visio or ERWIN)

5. Activity Diagram
6. Sequence Diagrams
   (To be developed using Rational Rose)
7. Architecture Design Diagram

1. Introduction (of analysis and design phase) (Virtual University Projects)

Analysis and design phase is the pictorial form of the system. With the help of provided diagrams, all processes have been shown pictorially. This pictorial form enables us to understand the whole system in easy way.  It will give a brief idea that how the project will work.

• DFD is graphically representation of the system that shows external entities and processes and show relationship between these entities. It has two part one is context diagram that show that show entire system as a single process and gives no clues as to its internal organization While level one DFD is detailed representation of the system.

• An entity-relationship diagram (ERD) is a data modeling technique that graphically illustrates an information system’s entities and the relationships between those entities. An ERD is a conceptual and representational model of data used to represent the entity framework infrastructure.The elements of an ERD are:

• Entities
• Relationships
• Attributes

• An activity Diagram specifies the coordination of executions of subordinate behaviors, using a control and data flow model. The subordinate behaviors coordinated by these models may be initiated because other behaviors in the model finish executing, because objects and data become available, or because events occur external to the flow. The flow of execution is modeled as activity nodes connected by activity edges.

• The Sequence Diagram models the collaboration of objects based on a time sequence. It shows how the objects interact with others in a particular scenario of a use case. With the advanced visual modeling capability, you can create complex sequence diagram in few clicks.

• Architecture views are representations of the overall architecture that are meaningful to one or more stakeholders in the system. The architect chooses and develops a set of views that will enable the architecture to be communicated to, and understood by, all the stakeholders, and enable them to verify that the system will address their concerns.

2. Overview (of proposed system) (Virtual University Projects)

• Examination is the most common assessment and evaluation technique in educational institutes. There can be many types of exams questions e.g. multiple choice, true/false, matching, short answer, essay, and oral etc.

• In normal conventional practices these exams are conducted on paper and marked by the teacher manually which makes it time consuming and full of expected human error.
• With the use of computer and internet, exam procedure has been automated. Now teachers prepare question paper online, which is presented to the students on their computer systems for solution. Students attempt the questions and submit the answers online which is marked by the teacher and the results of the exams are published online. The limitation that arises during this process is the scarcity of resources (computer systems).
• The solution of this problem is to utilize the mobiles phone technology. Now a day, each student has mobile with them in their classes. One can present MCQ paper to the students through GSM mobile using SMS facility.

3.Data Flow Diagrams (DFD) (Virtual University Projects)

.Context diagram
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
DFD Level 1:
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
4.Entity Relationship Diagram (ERD)
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
5.Activity Diagram
Sign Up:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
Sign In:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
Add Students &Add Degree Programmed :-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
Manage Account, faculty programmed and Students:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
Request to start paper:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
View Result and History:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )

6. Sequence Diagrams

Login and Sign Up:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
View history After Login:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
Request to start paper:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
Create Quiz and Check Quiz :-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
Add Student and their Semester:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )
Manage Degree,Faculty and Account:-
(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )

7. Architecture Diagram:-

(FOR DIAGRAM …….SEE THE ATTACHMENT FILE BELOW )

                                   vu-project-mobiquiz-design-1

0 0 votes

Article Rating

Subscribe

Login

Notify of

new follow-up comments new replies to my comments

Label

{} [+]

Name*

Email*

Website

Label

{} [+]

Name*

Email*

Website

0 Comments

Inline Feedbacks

View all comments