1. Identify stakeholder

- Student

- Lecture

- System admin

2. Identify Input, Process, Output

Student:

Input: login system, register subject

Process: Validate student, Validate student requirement to register, Select subject, Register subject, Display registered subject

Output: Print Slip

Lecture:

Input: login system, View student

Process: Validate lecture, Validate student, Display Student detail

Output: Print list student

3. Identify activities:

Process / Activity (Student):

Context diagram

Diagram 0: The processing system

Process / Activity (Lecture)

Context diagram

 

Diagram 0: The processing system

Learn more »

CONCLUSION

• The project has been appreciated by all the users in the organization.
• It is easy to use, since it uses the GUI provided in the user dialog.
• User friendly screens are provided.
• The usage of software increases the efficiency, decreases the effort.
• It has been efficiently employed as a Task management mechanism.
• It has been thoroughly tested and implemented.

Learn more »

FUTURE SCOPE OF PROJECT

          The application is capable of managing only tasks and their respective allotments where as there is not scope of communication between two groups or between the employees other than mail notification. The information between them is still in terms of documents. The application can improve in these areas of communication and document preservation as well as client maintenance. 

        The application can be converted into a Mobile with which the deployment of application will be done only on enterprises server and is accessible to all other departments of the organization. The current application is confined to only one enterprise.  Learn more »

PROJECT TESTING

1)    COMPILATION TEST:

• It was a good idea to do our stress testing early on, because it gave us time to fix some of the unexpected deadlocks and stability problems that only occurred when components were exposed to very high transaction volumes.

2)    EXECUTION TEST:

·         This program was successfully loaded and executed. Because of good programming there were no execution errors.

3)    OUTPUT TEST:

·         The successful output screens are placed in the output screens section.

Learn more »

Diagram 1.0
Compute Payroll

 

i.  List external entities.

       Employee

       Manager

       Foreman              

                               

ii.  Detect and show all errors in the diagram (SHOW THE ERRORS IN THE DIAGRAM ABOVE).

Diagram 1.0
Compute Payroll

 

E1:  No Input

E2:  no label name for data flow

E3:  process name should be verb not noun

E4:  not have data store label name

 

 


Learn more »