Welcome to Dream.In.Code
Getting Help is Easy!

Join 118,887 Programmers for FREE! Ask your question and get quick answers from experts. There are 2,080 online right now! We've got more than 500 tutorials and 2,000 snippets. Join and find out why Dream.In.Code is the #1 programming help community on the internet! Registration is fast and FREE... Join Now!



Using Software Model

 
Reply to this topicStart new topic

Using Software Model

aamir_mustafa2007@msn.com
post 23 Apr, 2008 - 09:42 PM
Post #1


New D.I.C Head

*
Joined: 3 Jul, 2007
Posts: 18


My Contributions


i want o implement a software model on the following scenario but i don't which is model is best
so kindly help me
Given Scenario
PakTech is a consultant company and is currently using an in-house developed Human Resource Information System (HRIS). The current HRIS do not covers the business of pre-employment which is being managed manually as well as other Human Resource department activities. Moreover this system has several issues that PakTech wants to resolve in new Human Resource Management System (HRMS).
Issues: Following issues have been identified in the current system.

CV submission
There is no automated system exists for CV submission from the candidates. Currently when PakTech requires a candidate for a particular post they give the ad in newspaper as well as advertise on their website. Also the HR dept of PakTech send the ad on different mailing groups like Rozee and PakJobsIT. In response to these ads interested candidates send their CVs through emails to the HR dept. The HR officer then manages these CVs, each as a separate file. So one of the issues is that there is no common format for CV submitted by the applicants therefore it becomes difficult for the HR department to identify and shortlist the required candidate for the interview.

CV Searching
Secondly CVs received by email and managed as separate files are not used for any future need because it is difficult to find a candidate of required qualification and experience from a collection of many files. As there is no CV searching facility available therefore every time company has to give the ad and repeat the whole process of CV collection from the applicants which is not only cumbersome but also a least productive exercise.

Conducting the interviews
Currently there is no automated system to schedule, track and arrange the interview as well as to manage the result status of the interview. The interview is conducted by a team of interviewers who give their report to the HR on paper. Moreover there is no automated way to schedule the interview and manage its progress which sometimes leads to misunderstandings and miscommunications between the HR and the concerned department about the time and day of interview.

Personal Information of an Employee
Currently the personal profile of a candidate is maintained in hard files and no automated system exits for the management of PakTech own employees’ profiles. The absence of an automated system has made the task of HR department difficult to maintain as they have to keep the record of many hard files in their office.

Benefits to the employees
Though company offer several benefits to the employee but employee usually don’t have full updated knowledge of these benefits. So employees are unable to get the updated information about the benefits offered by the company with time that results in un-availability of these benefits to the employees.

Training of Employees
The company usually gives training to the employees but HR dept use to organize these trainings but they don’t have an automated system to keep the record and manage the trainings in the company

Goal:
PakTech wants to resolve all these issues by developing a new Human Resource Management System (HRMS) so that all the necessary functions of HR department could be performed efficiently and effectively.

Assignment
Answer the following questions with respect to the scenario given above.
1. By considering the given domain and the issues of the current system you have to identify the Functional Requirements for HRMS (the new system to be developed).
2. PakTech wants the new system to be build with in a period of 3 months time. Suppose you are the Project Manger of this project and you have a team of 3-4 people. Which of the following software development lifecycle would you choose for developing this project and why?
• Water Fall Model
• Incremental Model
• Rapid Prototyping Model
• Rapid Application Development
• Spiral Model
• Extreme Programming
• Fountain Model
Justify your selection by giving solid arguments. You are also supposed to explain that why you have not chosen other SDLC models for building this application.
User is offlineProfile CardPM

Go to the top of the page


Martyr2
post 23 Apr, 2008 - 10:14 PM
Post #2


Programming Theoretician

Group Icon
Joined: 18 Apr, 2007
Posts: 4,669



Thanked 125 times

Expert In: C/C++, Java, VB, VB.NET, C#, PHP, Web Development, HTML & CSS, Javascript

My Contributions


Well they are not asking for which one is best, they are asking which would you choose and give arguments as to why you would go with that. So you could pick a few of them for various parts of the system.

Generally in a situation like this Rapid Application Development or Prototyping is a no brainer because the system is going to be used heavily by people and everything in the system is entered, manipulated by people working on "the front lines". Having said that, providing them with quick demo projects to feel out what works and what doesn't would be a great way to nail down the specifics. The client will have to play with some of the demos and try out the software workflow to see if it matches what they do as a company because efficiency is key (they want to process people in this system and the quicker and more efficient they can do that, the better. So workflow is key)

For the same reasons above I would also go with an incremental process. Demo something, let them try it, get their feedback, scrap what won't work, keep what will and then use that as the base to build bit by bit on it. That way you can keep getting the functionality out there and nothing will stop the work from continuing. You can have your team developing the features of the system that was last approved by the client while you are meeting with the client to get the next iteration of the project in place. It would be better than starting and stopping to collect information since you want the system on a 3 month time scale (which I think is pretty aggressive for a project like this).

But that is how I would tackle it. smile.gif
User is offlineProfile CardPM

Go to the top of the page

Fast ReplyReply to this topicStart new topic
Time is now: 10/13/08 03:16AM

Live Help!

Tutorials

Programming

Web Development

Reference Sheets

Code Snippets

Bye Bye Ads

Free DIC T-Shirt

T-Shirt Example

Related Sites

Monthly Drawing

Thumb Drive

Partners

Top Contributors

Top 10 Kudos This Month