Tiêu đề SPM-note.pdf ✅

Compiled by: Deepak Bhatta 3 b. Elements that accelerate user interaction, such as “hot keys”, “lists of suggestions”, and so on. c. Average time a user needs to perform individual actions. d. Support of accessibility for people with disabilities. 4. Reliability is an attribute of the system responsible for the ability to continue to operate under predefined conditions. Most often, the system fails due to the inaccessibility of external elements, such as databases, systems, and network connections. 5. Availability is part of reliability and is expressed as the ratio of the available system time to the total working time. Important indicators for this attribute are: a. Availability. b. Planned downtime. c. Time needed to update the software, and so on. 6. Security is responsible for the ability of the system to reduce the likelihood of malicious or accidental actions as well as the possibility of theft or loss of information. There are a number of measures that are used to protect systems: authentication, encryption, audit, and others. Examples of this attribute in the work of the system are: a. The ability of the system to detect DDoS attacks and respond to them. b. Restrictions of user access in accordance with authentication/authorization. c. Prevention of SQL injection. d. Encryption of passwords and content. e. Secure connection. 7. Maintainability is the ability of the system to support changes. Changes can be related to new business requirements or correction of old errors and affect system components or separate methods. Also, maintainability affects the time needed to restore the system after a failure. Excessive dependencies between components have a very negative effect on maintainability. 8. Modifiability determines how many common changes need to be made to the system to make changes to each individual item. Ideal is the case where each change affects only one element. 9. Testability shows how well the system allows performing tests, according to predefined criteria. In addition to testing performance, testability makes it possible to effectively divide the system into subsystems. The main indicators for this attribute are: a. Percentage of coverage with modular, integration, or unit tests. b. The final list of required test environments as well as the final list of used approaches to testing (manual/automatic, regression, integration, etc.) 10. Scalability is the ability of the system to handle load increases without decreasing performance, or the possibility to rapidly increase the load. There are two ways to improve scalability: a. Vertical: To increase, we add more resources, such as memory, disks or processors into one system. b. Horizontal: We increase the number of computing units and divide the load. 11. Reusability is a chance of using a component or system in other components/systems with small or no change. Allocation of responsibilities, modularization, decreasing of copy-paste are all about reusability. Copying code, or worse, using different components for the same result in different places, is one of the biggest problems of reusability. 12. Supportability is the ability of the system to provide useful information for identifying and solving problems. The main problems in ensuring supportability can be addressed with the following means: a. No diagnosis: How the activity and performance of the system are controlled. This includes various types of logging. bcanepaltu.com bcanepaltu.com
Compiled by: Deepak Bhatta 4 b. No tools for troubleshooting: This includes backups, various systems for creating snapshots of the system, and tools for auditing the system. When the system fails, it is always more pleasant to wait for an automatic restart than to solve the issue manually. c. No health checking: This includes a variety of systems for measuring compilation time, deployment time, database size, or mobile application size. A Software Project is the complete procedure of software development from requirement gathering to testing and maintenance, carried out according to the execution methodologies, in a specified period of time to achieve intended software product. Software Project Management is the art and science of planning and leading software projects. It is a sub- discipline of project management in which software projects are planned, implemented, monitored and controlled. Fundamentals of Software Project Management • clearly defining the vision for the end result • gathering the requirements in detail • breaking down the work effort into tasks • establishing measurable milestones that the team accepts • obtaining commitment on meeting the project objectives • tracking progress using metrics that are simple and fair • implementing quality controls that everyone understands • staffing the project appropriately to meet the project goals • selecting adequate tools and training to get the job done • assessing risks and mitigating them STAKEHOLDERS: These are people who have a stake or interest in the project. Stakeholders can be categorized as: ❖ Internal to the project team: They will be under the direct managerial control of the project leader. ❖ External to the project team but within the same organization: The project leader might need the assistance of the users to carry out systems testing. ❖ External to the both project team and the organization: External stakeholders may be customers (users) who will benefit from the system that the project implements. The relation here is usually based on contract. Stakeholders include ➢ The project sponsor and project team ➢ Support staff ➢ Customers ➢ Users ➢ Suppliers SP VS. OTHER TYPES OF PROJECTS ACTIVITIES COVERED BY SPM Many techniques in general project management also apply to software project management, but Fred Brooks identified some characteristics of software projects which make them particularly difficult: 1. Invisibility: When a physical artifact such as a bridge is constructed the progress can actually be seen. with software, progress is not immediately visible. Software project management can be the process of making the invisible visible. 2. Complexity: Per dollar, pound or euro spent, software products contain more complexity than other engineered artifacts. 3. Conformity: The 'traditional' engineer usually works with physical systems and materials like cement and steel. These physical systems have complexity, but are governed by consistent physical laws. Software developers have to conform to the requirement of human clients. It is not just that individuals can be inconsistent. Organizations, because of lapses in collective memory, in internal communication or in effective decision making, can exhibit remarkable, 'organizational stupidity'. bcanepaltu.com bcanepaltu.com