How Quality Requirements handling differ in service oriented and product-oriented software development? Is it possible that software requirements from product manager and project leader perspective are in conflict? How?
Please provide valuable suggestions.
Hi Unnati,
I think, it is possible.
If one of them wants product-oriented software (where to the customers already offering finished products with high quality, but wide use) but the other one wants service oriented software ( usually customized "Tаilor made" product) the conflict is ready.
Typical service-oriented software is developed by smaller companies that rely on revenue from a product that specializes in serving a specific business or activity, and has no ambition to multiply its product massively. In this case, emphasis may be placed on the details (Specific Quality Requirements), and the customer may have the feeling that he receives "special attention" and to think that the quality of the product are higher.
May be :-)
- Actually you mean Quality Management between Service and Good oriented development as you can find both of them in a "Product Orientation".
- Kindly note that the quality management for the good oriented is as the Quality Control (QC) which is the first control loop in a cybernetic model while the QM for the service oriented is as the Quality Assurance (QA) which is the second control loop in a double looped cybernetic model (inspired by Scott, 1998).
- Also please pay attention that the Organizational Management and the Leadership is not also in confliction with each other but also are completed each other and how better is that a manager be a leader too or in an organization, the managers work besides the leaders (Inspired by Robbins, 2016).
Requirements for software services typically come from end-user dept (for in-house IT dept ) , whereas for a software product they come primarily from Product Manager ( who prepares the same on the basis of requirements from target customers /marketing dept , after comparing with competitors) . It is the role of the Project Manager to discuss with the respective indentor (end-user or Product Manager , as the case be) and prepare a mutually acceptable requirements and prepare test cases out of them for use by his testing team. IT project delivery team must adhere to them while developing the software and testing team will use the same test cases for testing. Testing for software services projects is limited to functional and regression testing whereas in the case of software products, it has to extend to multiple hardware platforms and Operating Systems ( on which the software is targeted to be used). In some cases, code efficiency ( in terms of speed of execution) also needs to be tested for software products.
- Badges
- Science topic
- Similar topics
- Medicine
- Public Health