Project At ACT Medical SMS Center Management †Free samples

Question: Discuss About The Project At ACT Medical SMS Center Management? Answer: Introduction: Information system project management is the collection of processes for carrying out a complete ICT project with proper SDLC deliverables and protocols. In order to complete the project it is essential to use the software development life cycle model (Turner 2016). The software development life cycle model is consisting of activities like planning, designing, execution, testing and deployment so that each ICT project can be carried out successfully. The aims of the project are to provide a better insight of the operations ACT medical center and establish better communication among the doctor, nurse, management staff and receptionist. The objectives of the project are to prepare a Smart Medical System, properly allocate resources (financial, human resource and time) and deliver the SMS into the ACT medical center environment. The study holds the description of the schedule of the project, different SDLC models, selected SDLC model and justification, activities of SDLC, joiner system analyst development and recommendations. Discussion of the Project Schedule of Smart Medical System Project: The project schedule allows the project manger to establish proper communication among the tasks in the project through resource allocation and timeframe configuration. The project schedule reflects all the activities that are to be included within the project. The project schedule has a part called work breakdown structure (Schwalbe 2015). This reflects the hierarchical representation of the activities of a project management. Scheduling has a great impact on the financial aspects of a project, as it needs to be completed through allocating resources throughout all the activities. It is beneficial to enrich the documentation of the project. Types of SDLC Methodology: Waterfall Model: It is one of the oldest SDLC models. This methodology allows to move to the next phase only after the current phase is completed. It is a simple methodology and easy to use (Alshamrani and Bahattab 2015). This methodology is adequate for the small project development. V-Shape Model: This methodology can be considered as the modified version of the waterfall model. It is also known as the verification and validation model (Khan and Beg 2013). This model allows initiating the project tasks before completing another. Iterative Model: This model is repetition embodied. In this methodology, the first thing is working on small amount of software requirements (without having complete understanding of the requirements) and then testing, investigating and pointing out additional requirements. Spiral Model: It is assumed to be one of the most flexible methodologies of the SDLC models. The spiral models uses a cue from the iterative model and repeats it (Alshamrani and Bahattab 2015). The processes are carried out continuously until the outcome is achieved. Big Bang Model: The big bang model is the oddest among the methodologies of the SDLC. It does not include any specific process. As most of the resources are used for the development phase, there is a little effort to carry out the planning phase. Agile Model: The agile models delivers a working product with fast pace through breaking the product into cycles (Khan and Beg 2013). This model allows the project manager to insert new requirement into the system at any stage. Selection of SDLC: The current smart medical system project is a big and complex project. The smart medical system project manager has only two software developers. However, as the project is not about controlling the internal operations of the medical center, the complexity of the project is very high. Therefore, the smart medical system project can be done through simple methodology that can allow collecting requirements properly and then implement the product. There is still confusion regarding the quality of the requirement analysis phase (Alshamrani and Bahattab 2015). The project may not be complex enough to go for agile methodology but it is a big one and gathering requirements at once is not possible for small amount of employees. If the requirements of the smart medical system project are not met properly then the project may fail as waterfall model will not allow the team to go back to previous stage unless start from the beginning. This implies that only a flexible methodology will allow the project team to do it successfully. As per the project conditions, the iterative model is the best solution. The spiral model can a suitable for the SMS project but the complexity of the project may not be able to handle by the low project team members. The iterative model will allow the project team to adapt to the ever changing needs of both the clients and projects (Alshamrani and Bahattab 2015). As the project team has only two developers, it is essential to make use of the other team members too. The iterative model is the best solution for this concern. The iterative model allows the project manager to run various activities simultaneously. This will allow the Smart Medical System project to be completed quickly than a traditional SDLC model. The risks in this project is high. Therefore, managing the risks is a high priority factor in SMS project. SDLC Activities of Smart Medical System Project: The Iterative software development life cycle model has the following activities. Planning and Requirements: An initial planning stage is carried out then the software and hardware requirements. The planning phase consist of all the project stakeholder, internal and external (Kazim 2017). The requirements will be functional and non-functional. These requirements only be gathered within this phase. The main part will be creating schedule, risk management planning and other planning tasks. Analysis and Design: After the completion of the of the smart medical system project planning phase, the requirements are analyzed for identifying proper business logic, project constraints, database models, software architecture and many more. Within the design phase, additionally, the technical requirements are established. The interaction among the users and system will be analyzed and determined in the design phase. The system analyst will investigate the gathered information form the users and create the system requirements of the system. Implementation: The actual developmental of smart medical system project work of the project is carried out in this phase. The implementation phase of the project is the most crucial. The developers work on the designs and implements the requirements into logically operating functions (Kazim 2017). The implementation phase will be consisting of activities like database development, software development, web development and mobile application development. Testing: This phase can be referred to as the checkpoint of the implementation phase. Each and everything built in the implementation phase, is tested in the testing phase. In this phase, the integrity, functionality and scalability of the functions are checked. Evaluation: After the completion of all the stages, the thorough analysis of the development up to the testing phase is done (Sarker et al. 2015). This allows all the stakeholders, internal and external, of the smart medical system project to identify which of the requirements are met and which are not. Techniques, Models and Tools for Support SMS Development: Techniques: Recognizing and Understanding Customer: The project manager will need to recognize the users of the system. In this case, the users are current and potential patients, doctors, nurses, management staff and receptionists. Identification of Deployment Strategy: There are mainly two types of deployment strategy such as direct and passive (Senathi, Vinod and Jadhav 2016). The project manager of smart medical system project must be able to select either of the deployment strategies. Installation Testing: The smart medical system project should test the installation script as the smart medical system will be tested after development. Models: UML Diagrams: The UML diagrams will be very assisting in this OOP. The UML diagrams will allow the project team to identify the system functionalities and boundaries. It provides standards for the development of the software. Less time for development. ERD: The entity relationship diagram will allow the developer of smart medical system project to design the database. Creating the ERD is a very easy process. The visual presentation of the database becomes very good through the use of ERD. Among the domain experts, users and database designers, it is a very good communication tool. Tools: Feature Oriented Software Development: FOSD can be used to plan and implement SPLs as well as to select features and generate customized programs (Kastner and Apel 2013). FeatureIDE supports the FOSD process and it is distinguished between the following four phases. Domain Analysis Domain Implementation Requirement analysis Software generation Oracle Database Software: In order to develop the database, the smart medical system project team will be using the Oracle Database Developer application tool. The Oracle provides better security. Oracle database provides the opportunity of online backup and recovery. Moreover, the advantage of it is able to handle good fault tolerance to disk failure. Web Development Tool: There are various web development tool that can be used for developing the website. The most preferable in terms of cost efficient development is php and in terms of security JSP is the best tool. The Java Server Pages are best for developing the most secured pages. Both of the PHP and JSP are able to allow creating dynamic pages. If the project is running short on time and security concerns may be neglected then PHP is the best option. Moreover, developing php pages are cost efficient too. Joiner System Analyst Advertisement: ACT medical center and Canberra Software Development is a huge medical treatment center. The AMC and CSD anticipate a five-month development schedule for an initial version of the server software and android-based client-side software. There month period for the design and code development and finally two month for the testing. In this systems analyst role you will become part of a large team working to meet the needs of both internal departments and external clients. Responsibilities: Analysing operations and interpreting the associated system requirements for a range of online banking initiatives Designing efficient and effective financial and client management systems from the ground up Writing technical specifications and liaising with IT staff and providers Budgeting and analysing phases of systems implementation for internal initiatives and external clients Working with software designers to understand product application and potential limitations, including system testing Conclusion: From the above study, it can be concluded that the Smart Medical System project at the ACT medical center is a big but simple project. This type of combination is rare in projects like ICT implementation. The scheduling allows the project manager to have better understanding of the project deliverables. There are two types of methodologies, adaptive and predictive. This project is best suited to adaptive approach as gathering initial data to start the project is very hard for small amount of employees. Each and every part of the study has been done properly with adequate data. The software development life cycle are particularly developed for the software development projects. Not all the SDLC approaches are suitable for every project. In order to identify the most suitable method, the project manager conducts analysis and compares all the approaches. Recommendation: Proper Resource Allocation: The resource allocation is one of the biggest issues in big projects. The project manager must be able to properly distribute the resources to each and every task. Proper Scheduling: Scheduling is one of the biggest factors in the project success and failure. The scheduling must be done with proper timeframe and resource distribution. Cost Benefit Analysis: The cost benefit analysis allows the project owner and sponsor to identify whether the project is capable of providing any benefit to the organization. Risk Management: The project manager must be able to manage the potential risks of the project. From the identification to analysis, each parts of Risk Management must be addressed. Selection of Project Deliverable: Project deliverables are a crucial part of the project. The project manager along with the other team members creates the deliverable of the project so that project can be completed efficiently. Proper Working Environment: The project manager will be responsible for manging the working atmosphere. Project manager will resolve the issues within the team members and all maintain the environment Reference List: Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall model, spiral model, and Incremental/Iterative model.International Journal of Computer Science Issues (IJCSI),12(1), p.106. Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall model, spiral model, and Incremental/Iterative model.International Journal of Computer Science Issues (IJCSI),12(1), p.106. Kastner, C. and Apel, S., 2013. Feature-oriented software development. InGenerative and Transformational Techniques in Software Engineering IV(pp. 346-382). Springer Berlin Heidelberg. Kazim, A., 2017. A Study of Software Development Life Cycle Process Models.International Journal of Advanced Research in Computer Science,8(1). Khan, P.M. and Beg, M.S., 2013. Extended decision support matrix for selection of sdlc-models on traditional and agile software development projects. InAdvanced Computing and Communication Technologies (ACCT), 2013 Third International Conference on(pp. 8-15). IEEE. Sarker, I.H., Faruque, F., Hossen, U. and Rahman, A., 2015. A Survey of Software Development Process Models in Software Engineering.International Journal of Software Engineering and Its Applications,9(11), pp.55-70. Schwalbe, K., 2015.Information technology project management. Cengage Learning. Senathi, A., Vinod, G. and Jadhav, D., 2016. Software Reliability Based on Software Measures Applying Bayesian Technique. InProceedings of the Second International Conference on Computer and Communication Technologies(pp. 167-173). Springer, New Delhi. Turner, R., 2016.Gower handbook of project management. Routledge.