Delivery in day(s): 4
Database Information System Assignment Help
The database information system assignment help scope of this project is to simplify the operations in Millennium Furniture Company to handle the employee salary system, purchases and orders effectively. The project is also planned with intention that it will solve the extra efforts on business management with traditional approaches. It will bring the business into new dimensions of information management where the workplace will be productive and responsive with quick access to resources (Kerzner, 2013). The main scope of project is to facilitate the company with easy management of business operations and to empower the decision making in workplace with correct analytical results of business activities.
Functional and non-functional requirements
In order to achieve the fully working system for company, it is required to analyse the requirements of company which may be functional and non-functional in nature. Functional requirements are those have contribution in delivery of projects and have link with the services demanded in project by company. Non-functional requirements are supplementary and have support for primary functioning of project in workplace.
The project needs to collect the requirements from company workplace to determine the exact need of system to cover the issues in operations. For instance, company is facing problems to manage the orders those are incomplete due to incomplete payments. Also the requirement of new system is being in practices due to difficulties to search the loyal customers from years, actual requirements in an order, cost estimation etc. All this requirements needs to collect the requirements of company for operations with proper analysis of business structure and processing. The company also need to clarify the requirements with pay system, working hours, order placing, minimum deposit and material requirements for specific products. Addition to it, information related to technology for new system need to be analysed to use in company (Chung.et.al.2012).
The functional requirement also need to determine with the data storage, technology to implement and functions to cover in system so that a robust system can be designed to meet the goal of company to simplify the workplace load and effort. Functional requirements also summarize the requirements of company for isolated or network system according to their workplace processing.
Functional requirements are required at developer side to design the project but non-functional requirements also need to be defined clearly to get the project complete within constraints of company. For that, financial and technical supports from company must need to be analysed as non- functional requirements. Company also need to clarify the skills of employees and future investment on product as well as on employees to work well with project. Addition to it, future requirements of company must need to be analysed. Also the additional services like printing and server can be installed with project to make the work easy and effective within time. Project also offers the features those can direct the users towards the use of capabilities of project. Company can provide the minimum functionality and cost for the project to accomplish it economically (Ameller.et.al.2012). Company can provide information about the time in which project is expected, the business constraints like cost and user skills and requirements of network and security with project.
The entire project can be modularized into few numbers of related modules so that project can be managed and tested well with requirements of company. Project is planned to be finished in 4 weeks where every week has number of task to complete. In initial week, it is required to study the feasibility of company in term of financial and technical supports in development of project. It also includes the study of company for the workplace conditions in which project need to implement. The project team also analyse the all possible number of solution in which company can fulfil the requirements in cost effective manner. User skills and working manner is also considered in feasibility study to safe guard the system. Later the requirements of company will be listed and updated with time to meet all the goals properly in project design (Burke, 2013). For that, users and governing bodies can be interviewed and consulted for features and expectation in new project.
Entire project team can be divided into modules to handle the responsibility of each job assigned to them. This may require the analysis of project team for the skills and capabilities. The employees also can be involved in project design if they are skills to handle some task. Prototype can be designed to meet the requirements of company and it will help to suggest new ideas from non IT staff in workplace. Every module can be tested separately and combine to validate the functionality and features in final version. Methods and techniques can be documented for future updates in project (Meredith and Mantel, 2011). Addition to it, the project will be audit for erroneous data insertion and security in testing and will be mark for future implementations in project. Although week and planning can be grouped to parallelize two operations in project design which will reduce the total time on project completion.
The projects which will be back end by database for company need to estimate the cost of completion. Proper analyse of cost and benefit is required to determine the effectiveness and acceptance of project in workplace. It has been clear that company has limited number of systems and users are also not aware to work with electronic systems to regulate the business. Al though the work needs to be handled at centralised location in company so that it can be secure for unauthorised access and damage. For the calculation of cost, following factors can be determined exactly.Estimation of cost and benefits
- The requirement of technical support and experts. The cost of one team member can be multiplied to number of team members in same field. The summation will indicate the cost on technical staff.
- Cost associated with equipments and tools to design the system.
- Cost associated with installation and implementation.
- Cost of training and development of employees to interact with system (Shepperd and MacDonell, 2012).
- Addition cost of supplementary services like mail system and internet.
The summation of all the cost distributed with multiple requirements may give an idea to company for the total cost of project. Cost estimation helps company to determine the capabilities to manage and run with project. This is also required to avoid the future confliction in payment system and loyalty with company. Cost estimation gives an idea to company to arrange the resources and to modify the structure for more revenue.
However, the cost will not be larger for company to manage the work in productive manner. The traditional approach of company to process bills and invoices, generation of orders and payment system looks cost effective but it was time consuming and company had hidden investments of capital and efforts in it. With the cost effective project, company will have following advantages:
- Calculation of working hours: Andrew can focus on primary business activities when calculation of employee’s working time along with adequate wages and deductions for funds will be easy. At end of month, Andrew can the exact number of working hours and payment as software system will calculate the time and values of time in work for every employee.
- Management of orders: The system will be capable to notify the customers for their dues in payment and requirements automatically after the specified time. So company will save a lot of time to identify the faulty customers and to notify them (Bryde.et.al.2013). If the requirements do not meet, system will be capable to cancel the orders with confirmations.
- Generation of invoices: Invoice generation and storage will be effective with project as it will use database in back end to store the information for easy retrieval and storage purpose.
- Inventory and product management: company will get facilities in inventory management so that new entries for products can automatically check for number of requirements. If the raw material is in inventory then new orders can be placed.
- Logging: company will get effective system to log the receipts and business documents in centralised system with back up.
The project is expected to deliver on time with required features and functions but the following risks are appearing as barrier for project completion.
- The target users in company are not satisfied with the implementation of project as they are not so skilled to understand their requirements and demands easily. The addition of new requirements with project has slow down the progress of completion.
- Another project risk is the cost. The overall cost including the cost of the engineer and technology has gone above than the budget prepared for the project before its starting. The reason behind this increment is the unnecessary changes made frequently to the prototype. This leads to the requirements of more resources in order to make the project according to the expectations of the users. The other miscellaneous expenses like cost of transportation, preliminary expenses, etc (De Bakker.et.al.2013).
- The current project risk also includes the time factor. The users of Millennium Furniture Company are not well aware with their needed requirements and because of this they are giving their demands and requirements related to the software again and again and due to this the prototype so developed is required to be modified according to their new demands and requirements. This leads to unnecessary wastage of time in developing a modified working prototype.
- Due to some of the business constraints the development of the project is slow down. In order to develop effective and helpful software many of the information and permission is needed by the owner of the company. But the owner of the Millennium Furniture Company is not supporting well and due to this many of the hurdles and difficulties are coming in the way of completing the project successfully and timely (Mojtahedi.et.al.2010).
Project Work Breakdown Structure
The project can be divided into manageable tasks so that team members and their skills can be used properly. Work break down structure also helps to test the functionality and features so that every task can be updated separately to save the time and cost. Also the parallel processing of task helps to deliver the project within time with required quality. The entire work breakdown structure is shown below which indicate that project is divided into four modules which are also further divided according to the skills of team members. This is top down structure to break down a work in which project is formed from bottom to top approach for integral form (Straub.et.al.2013).
Work break down approach helps to assign the job to specific team members those will be solely responsible for their work. Also work can be managed more effectively. For instance, when project is under design, prototype can be designed according to requirements of users to make it include in project development later. In this manner, overall productively and performance increases in workplace. Entire team can be divided according to modules of project and time line can be specified to deliver the output to next team group. For instance, requirement gathering team can complete the work for enough requirements to initiate the project and then handle the requirement gathering and design task with another team.
Project Critical Path
Project Tasks are:
Design and development
Critical path for the project is:
Ameller, D., Ayala, C., Cabot, J. and Franch, X., 2012, September. How do software architects consider non-functional requirements: An exploratory study. In 2012 20th IEEE International Requirements Engineering Conference (RE) (pp. 41-50). IEEE.
Bryde, D., Broquetas, M. and Volm, J.M., 2013. The project benefits of building information modelling (BIM). International Journal of Project Management, 31(7), pp.971-980.
Burke, R., 2013. Project management: planning and control techniques. New Jersey, USA.
Chung, L., Nixon, B.A., Yu, E. and Mylopoulos, J., 2012. Non-functional requirements in software engineering (Vol. 5). Springer Science & Business Media.
De Bakker, K., Boonstra, A. and Wortmann, H., 2010. Does risk management contribute to IT project success? A meta-analysis of empirical evidence. International Journal of Project Management, 28(5), pp.493-503.
Kerzner, H.R., 2013. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.