Which sdlc model for employee information system

Once the organization has selected a vendor and finalized the contract, it should conduct more due diligence to ensure a successful implementation. Understanding the HRIS end users' needs, technical possibilities, software parameters, and the implementation process will increase the probability of rolling out a system that meets HR and organizational needs. First, identify and document the underlying objective for the new HRIS. This involves determining which pieces must be implemented versus which would be nice to have.

Keep in mind the organization's size, number of employees and overall scope of deliverables. No matter how thoroughly an organization prepares for an HRIS implementation, things could go wrong. Some of the most common problems encountered when implementing technology projects include scope creep of the deliverables, poorly defined requirements resulting in rejected deliverables, late delivery or poor communication between stakeholders, project management and vendors.

A strong project implementation team will identify problems early on to keep the project on track. After implementation, the organization and vendor should conduct system testing, often concurrently with data migration and configuration, to verify data integrity.

Are the data stored in the correct location? Can users query the data? Are the data available to individuals with appropriate security clearance? Technical software team members should test each module for proper functionality, and functional HR team members should verify that the module is working properly and maintaining data integrity. Some organizations opt to change over to the new system immediately, turning off the old system.

Adjustments are made as needed when problems are identified during testing and initial use. The potential downside to this approach is the organization-wide learning curve as users adjust to the new software. Another option is to run both systems concurrently, waiting a defined period of time e. A parallel change allows for significant testing before the old software disappears. To help support and validate the new system's value, organizations should identify the lessons learned from the implementation and share them with management.

What worked? What did not work? Which areas need improvement? Finally, create and adhere to a schedule of measurement or identification of milestones and related reporting during the planning process and assign a dollar value to each critical step to evaluate budgets.

You may be trying to access this site from a secured browser on the server. Please enable scripts and reload this page. Reuse Permissions. Page Content. You have successfully saved this page as a bookmark. OK My Bookmarks. Please confirm that you want to proceed with deleting bookmark. Delete Cancel. You have successfully removed bookmark. Delete canceled. Please log in as a SHRM member before saving bookmarks. OK Proceed. Your session has expired.

Please log in as a SHRM member. Cancel Sign In. Please purchase a SHRM membership before saving bookmarks. OK Join. An error has occurred. Waterfall works well with inexperienced staff. The application type is well known to the company, so a thorough user requirements analysis should be possible early on. An existing application is to be re-engineered. This also confirms that the user requirements are known early. They could be extracted from the existing application. The company will maintain the software, so good documentation will be essential.

The company has a good reputation to maintain in this area, so quality control will be essential. Waterfall emphasis of requirements-before-design and design-before-coding will emphasise quality. Weaknesses: Waterfall has no obvious weaknesses on this project. We may end up swimming upstream, but the chances seem minimal since the requirements should be clear from the start.

Late arrival of code may be one, but on the other hand our client may be able to continue using the existing application until the new system arrives. Solution 1 b : Functional and Non-Functional requirements Interface Requirement, This section defines the parameters that the software product must follow while interacting with the outside world.

User Interfaces : 1. Login Screen 2. The model implemented by us is Waterfall Model, which is most widely used in procedure-oriented development. This model attempts to break up the identifiable activities into series of actions, each of which must be completed before the next begins. The activities include problem definition, requirement analysis, design, coding, testing, maintenance.

Further refinements to this model include iteration back to previous stages in order to incorporate any changes or missing links. The phases and the outputs of the waterfall model at each phase are summarized below in tabular format.

Software development life cycle process specifies a method of developing the software. Each software development projects starts with some needs and ends with some software that satisfies those needs. A software development life cycle specifies the set of activities that should be preformed to go from user needs to final products. There are different models of SDLC process and each model specifies the activities and the order in which they should be preformed. Depending on the nature of project, a suitable model is chosen and the entire process of software requirement analysis, design, coding, testing and maintenance is preformed accordingly.

This model attempts to break up the identifiable activities into series of action, each of which must be completed before the next begins. An initial investigation culminates in a proposal that determines whether a system is feasible or not.

It determines its workability, impact on the organization, ability to meet user needs, and effective user resources. The objective of feasibility study is not solve the problem but to acquire a sense of its scope. During the study, the problem definition is crystallized and aspects of the problem to be included in the system are determined.

Consequently, cost and benefits are estimated with greater accuracy at this stage. This is a bridge in between the User Requirements and the output that he can avail under a set of given constraints, inputs and outputs.

The main steps are :. Statement of constraints. Identification of specific system objectives.