Online Project Tracking System
The project “Project Tracking System” is the System, used to know the current positions with the employees working in a software company. This software makes us the employees in software Company to know their current working speed and efficiency of how he or she works. This system also tells us how efficiently the company works goes on and the implementation of this kind of system tells how efficient and accurate the company is and whenever a customer ordered for software package how fast the company returned it back.
The main key in designing the project is to maintain the records ie., tracking employee records how many employees in the company work.
The Project Tracking System has been undergone testing using the below testing techniques. The unit testing, integration testing and system testing are carried out and the system is found satisfactory. And the main concept of this project is that what are all the roles presented in a software company to finish a software project successfully.
The main aim of the project is to develop a full Network security and Admin tool. Net watch is in its earlier stage of development. It should be optimized for performance.
PROJECT OUTPUT VIDEO:
In the existing system, we have got some anomalies in some ways, like lack of perfect validations.
Considering the anomalies in the existing system computerization of the whole activity is being suggested after initial analysis by the organization.
The proposed system keeps the records of the employees more perfectly, as there will be some hundreds of employees, joining and resigning continuously, every day, maintaining the details more perfectly needs to be focused. I would like to keep more validations to get the data updated each time a record gets changed, in all the files. I would like to have some more reports based on different conditions.
The user who wants to use the system should have the view about the employee details and he should be able to get a complete idea about the system.
Based on the above proposals the project of the Human Resource Management system can be much more improved. Enhancements can be made to the existing system to make it more users friendly.
The objective of the project is to develop software according to the customer requirement by the Software Development Department.
The project since contains the screens for entries, and reports, the data can be entered, retrieved and reports can be generated. The back end is maintained to store the data and to retrieve the data. Validations are kept both in back end and front end in order to facilitate users an idea to enter correct data. For example, if the user is entering the incorrect data, he is given an error message and allowed to again enter the perfect data.
- Task Assignment
- Identifying Who to Contact
- PR Work
For accountability purposes, all changes in the Alpha software need to be associated with a problem report . Among other pieces of information, a PR describes the changes in the code, the reason for the changes (bug fixing, enhancement, etc.), and who made the changes. An Alpha developer is delegated new tasks by being assigned to work with one or more PRs. These PRs are reported by other team members. Whoever is filling in the PR is responsible for filling in the field “how to repeat,” which describes the circumstances (data, tools, and their parameters) under which the problem appeared. When software developers report a PR, they also might divide a PR into multiple PRs that achieve the same goal. This division aims to facilitate the organization of the changes in the source code, separating PRs that affect the released Alpha tools from those PRs that affect tools or processes not yet released.
As mentioned in the previous section, each developer is assigned to one or more processes and tends to specialize in that process. A manager will follow this practice and assign developers to work on PRs that affect “their” respective processes. However, it is not unusual to find developers working in different processes.3 In this case, Alpha developers need to identify and contact the process owner to find out whether there is a problem in the process. 4 If there is a problem, developers will start working to find a solution to this problem. Even if the problem is straightforward, before committing their code, Alpha developers need to contact process owners to verify, through a code review (a prescription of the Alpha software development process), whether their changes in the process are going to impact the work of these process owners. Code reviews are performed by process leaders whose processes are affected by the changes in the PR. If the changes involve more than one process, a request for a code review has to be made to the owner of each process affected by those changes.
Identifying Who to Contact:
The need to contact process owners means that the developer working with the PR needs to identify the owner of the process being affected. This is not a problem for most developers, who have been working in the project for a couple of years and already know which developers work on which parts of the source code. In contrast, developers who recently joined the project face a different situation because they lack this knowledge. To handle this situation, newcomers use information available in the team’s mailing list. The software development process prescribes that software developers should send email to this list before integrating their changes in the shared repository. Developers thus associate the author of the emails describing the changes with the “process” where the changes were occurring: Alpha team members assume that if one developer repeatedly performed check-ins in a specific process, it was very likely that he or she was an expert on that process. Therefore, a developer needing help with that process would know who to contact for help.
After having his or her changes approved by the process owner(s), a developer fills in the other fields of the PR, describing not only the changes made in the code (through the designNar field, for example), but also the impact these changes are going to have on the V&V staff.The information about the impact on the V&V staff is re- corded in two PR fields: (i) the “how-to-test-it” field is used by the test manager, who creates test matrices that will later be used by the testers during the regression testing; and (ii) another field that describes whether the Alpha manuals need updating. The documentation expert uses this information to find out whether the manuals need to be updated, based on the changes introduced by the PR. In some cases, developers are even more specific.
System : Pentium IV 2.4 GHz
Hard Disk : 40 GB
Floppy Drive : 1.44 MB
Monitor : 15 VGA color
Mouse : Logitech.
Keyboard : 110 keys enhanced
RAM : 256 MB
O/S : Windows XP.
Language : Asp.Net, c#.
Data Base : Sql Server 2005.