Software for a Library
Step 1: Determine the facts in the situation – obtain all of the unbiased facts possible
Implementing a library system is one of the most advantageous steps in managing the materials in and also the materials that have already been given out. Confidentiality is one of the most requirements in a library system where the librarian is the only individual who can and has the permission to access certain files (Rozanski and Woods, 2012). An overview advantage of having a software system for library management is that even the cost of running the library reduces by half since the automation of every duty conducted will reduce the manpower need and replaced with a timely software that will enhance the record keeping, disbursement, and also requesting a return or extension of materials given out to individuals (Zykov, 2016). Security is assured where the librarian can set up passwords in order to access the files in the system. This is greatly enhanced by the fact that a high level of encryption is used to secure the details in the files ones they are saved through an individual password.
Step 2: Define the Stakeholders - those with a vested interest in the outcome
Stakeholders in a system development are broad since it involves the individuals or all parties which have the interest in the development of the said system (In Chen et al., 2014). In this case, stakeholders can be the librarian, the owners of the library, the software developers, and also the users who all in this section send representatives. Involving every interested party in software development assist in eliminating doubt about the software developed since each party has suggestion and questions on what is the cost, how to implement the system, and also what features the software should contain (Rozanski and Woods, 2012). Stakeholders also assist in determining the cost of developing the required system since the requirements vary and therefore the cost will also vary. The system can develop problems after installation and therefore having involved the stakeholders will reduce the risk of developing problematic issues in the end.
Step 3: Assess the motivations of the Stakeholders - using effective communication techniques and personality assessment
The motivation of the stakeholders and mostly the owners of the system are to have effective software that fulfills the wants of every individual and contains the features which are easy to understand. Stakeholders have the choice of owning a system by which the running of the system is cheap and also reduces the tasks around the library (Zykov, 2016). Certain responsibilities such as keeping record on who has what and which item is due becomes easy since the software can be integrated with mobile numbers of every individual who has borrowed any item and when it is due, a text message or an email is sent to the individual and it reflects in the system. The system will enhance the effective storage, privacy, and also security of data stored in the systems.
Step 4: Formulate alternative solutions - based on most complete information available, using basic ethical core values as guide
An alternative solution for the library system would be to improve the record keeping in a much cheaper way through developing a simple database and or using a software system (In Chen et al., 2014). The database can act as a record keeping system where the names, details, items, and the items given out can be stored. It is a much cheaper method where the database can only be accessed and operated by an expert and therefore privacy is enhanced (Shaw et al., 2012). Also, the cost of a database is much cheaper and less complicated steps compared to software but the software can perform more options than a simple database.
Step 5: Evaluate proposed alternatives - short-list ethical solutions only; may be a potential choice between/among two or more totally ethical solutions
The option on developing a database is much ethical and no technology expertise is required in the development of a simple database. The steps involved in the development are simple to understand and therefore the librarian can follow the simple steps and finally adapt on how well to manage the record, and also improve the efficiency in terms of service delivery (Zykov, 2016). Testing must be carried out in the development in order to eliminate the risk of difficulties in operating the database.
Step 6: Seek additional assistance, as appropriate - engineering codes of ethics, previous cases, peers, and reliance on personal experience, prayer
The option is much more affordable and easy in terms of maintenance. The only difficulty which can lead to a failure of the systems is the common mistakes that are made by the developers when developing a database since one error can lead to a collapse of the whole system (Shaw et al., 2012). These mistakes such as leaving out vital information and keys in development can lead to a problem in future where the database is required to produce certain information on certain records but due to a lack of a proper command to that request, the information cannot be obtained.
Step 7: Select the best course of action - that which satisfies the highest core ethical values
Software is much more preferred than a database. Software’s tend to have more features and therefore enhance the work delivered to the final users. The privacy of customer requirement is highly confidential between the client and the software developer and even a pilot method can be used in order for the customer or the owner can see the type of software developed (Shaw et al., 2012). This makes it even more comfortable to choose the software system since certain changes can be done before even the system is put into test or even implemented.
Step 8: Implement the selected solution - take action as warranted
Implementing software becomes an easy task when the developer has the expertise in this section. There are a series of processes that are followed during software implementation and therefore maximum attention is needed here. The steps followed are in the form of phases beginning with planning, analyzing, design, configuration, testing, implementation, and finally maintenance. The outlined steps are very important in software development and implementation since they eliminate the risks involved where obsolete systems can cause a failure (Rozanski and Woods, 2012). Testing the system is one of the important steps since the data is collected on how the system operates, what new features are available in the system, and which abnormal reaction is observed by the developer.
Step 9: Monitor and assess the outcome - note how to improve the next time
After the implementation of the system, a follow up is done to ensure that the system does not develop complications at a later stage but to develop the complications once it has been implemented. The data that was in the book records has however been fed into the system and therefore the system has already started operation (Zykov, 2016). The results obtained after the system has started operation will be collected and clearly checked into to ensure that the system works effectively and according to customer requirements. The developers provide the owner with certain patches which can be used in the software as changes takes place in the system. Security risks and bugs are also identified and corrected timely. The information corrected is therefore used to improve the system and to make the developers aware of how the system works when tasked with certain tasks (Rozanski and Woods, 2012). This is very important since the issues noted will be used in improving the system when developing a system next time. The issues are taken into consideration in order to develop a software that has zero errors and which operates accordingly.
References
In Chen, X., In Wang, Q., & In Luo, Y. C. (2014). Reading development and difficulties in monolingual and bilingual Chinese children.
Rozanski, N., & Woods, E. (2012). Software systems architecture: Working with stakeholders using viewpoints and perspectives. Upper Saddle River, NJ: Addison-Wesley.
Shaw, C. B. T. J. B. G. B. J. B. C. (2012). Pro SQL Server 2012 Practices. Springer-Verlag New York Inc.
Zykov, S. V. (2016). Crisis management for software development and knowledge transfer.
