scholarly journals ELICITATION, REPRESENTATION AND MANAGEMENT OF SOFTWARE DESIGN KNOWLEDGE

2011 ◽  
Author(s):  
Behrouz H. Far ◽  
Mohsen Afsharchi
Keyword(s):  
Software Development ◽  
Project Manager ◽  
Prototype System ◽  
Software Development Process ◽  
Multiple Stakeholders ◽  
Types Of Knowledge ◽  
Decision Making Processes ◽  
Context Specific ◽  
Descriptive Knowledge ◽  
Coding Rules

In this research we focus on understanding the nature of the knowledge used during the various phases of the software development process. We have found that there are two types of knowledge involved in software development: (1) descriptive knowledge represented by conversion and coding rules, e.g., a rule for splitting a class into two; and (2) prescriptive knowledge required for deployment of global or local strategies at a micro design level; e.g., knowledge required to answer the question “why should a class should be split into two?” Most of the already existing knowledge management solutions address descriptive knowledge. Elicitation and management of the prescriptive knowledge is difficult in the sense that it is probabilistic, personalized, distributed and context specific. Also we have found that prescriptive knowledge tends to be used in decision making processes involving multiple stakeholders with different perspectives (e.g., designer, tester, software architect and project manager). We also report on a prototype system called ISS-OKM to extract and reuse both the descriptive and prescriptive knowledge.

A New Framework for Improving Software Development Process on Small Computer Systems

1997 ◽  
Vol 07 (02) ◽  
pp. 171-184
Author(s):  
Makoto Sakai ◽  
Ken-Ichi Matsumoto ◽  
Koji Torii
Keyword(s):  
Software Development ◽  
Process Improvement ◽  
Development Process ◽  
Computer Systems ◽  
Project Manager ◽  
Small Computer ◽  
Software Development Process ◽  
Development Processes ◽  
Development Risks ◽  
New Framework

While small computer systems have provided us with a wide array of development and operational environments, implementation methods, and domains of the software to be developed, it has also made the software development more risky. This paper proposes a new framework for improving the software development process on small computer systems to reduce software development risks. The key idea of the proposed framework is that the solutions to the software development problems can be extracted by the project manager, with relatively low overload, from the development processes that were actually executed in order to reduce the development risks, and then be formalized and stored in a database. The formalized solutions can be used not only for process improvement, but also for devising new solutions if new problems should occur in the future. We believe that the proposed framework is capable of making up for the difficulties in implementing CMM on small computer systems, and it encourages us to apply CMM to such risky software development.

Optimization and practice of requirement analysis based on prototype portrait in software development process

2021 ◽  
pp. 1-9
Author(s):  
Mingyu Yue ◽  
Haiyan Feng
Keyword(s):  
Software Development ◽  
Requirements Analysis ◽  
Prototype System ◽  
Requirement Analysis ◽  
Software Development Process ◽  
Functional Requirements ◽  
Analysis Method ◽  
Development Cycle ◽  
Requirement Document ◽  
Software Requirement Specification

Aiming at the problems of incomplete description, ambiguity and inconsistency in the traditional requirements analysis method based on prototype system in software development, this paper proposes a requirement analysis method based on prototype portrait, introduces the process of obtaining the software requirement specification and designing the software by using the prototype portrait method according to the user’s requirements, and formalizes the process of the method, and develops the software with the prototype portrait requirement document approved by the customer, so as to ensure the correctness of the designed functional requirements. The practical results show that the requirement analysis method based on prototype portrait overcomes the problems of long development cycle and high failure rate existing in the traditional requirements analysis method of prototype system, and improves the quality and cycle of software development.

Computable metrics of personal performance in software development teams

2019 ◽  
Author(s):  
Andriy Lishchytovych ◽  
Volodymyr Pavlenko
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Product Quality ◽  
Performance Indicators ◽  
Key Performance Indicators ◽  
Project Manager ◽  
Development Life Cycle ◽  
Software Product ◽  
Software Development Life Cycle

The present article describes setup, configuration and usage of the key performance indicators (KPIs) of members of project teams involved into the software development life cycle. Key performance indicators are described for the full software development life cycle and imply the deep integration with both task tracking systems and project code management systems, as well as a software product quality testing system. To illustrate, we used the extremely popular products - Atlassian Jira (tracking development tasks and bugs tracking system) and git (code management system). The calculation of key performance indicators is given for a team of three developers, two testing engineers responsible for product quality, one designer, one system administrator, one product manager (responsible for setting business requirements) and one project manager. For the key members of the team, it is suggested to use one integral key performance indicator per the role / team member, which reflects the quality of the fulfillment of the corresponding role of the tasks. The model of performance indicators is inverse positive - the initial value of each of the indicators is zero and increases in the case of certain deviations from the standard performance of official duties inherent in a particular role. The calculation of the proposed key performance indicators can be fully automated (in particular, using Atlassian Jira and Atlassian Bitbucket (git) or any other systems, like Redmine, GitLab or TestLink), which eliminates the human factor and, after the automation, does not require any additional effort to calculate. Using such a tool as the key performance indicators allows project managers to completely eliminate bias, reduce the emotional component and provide objective data for the project manager. The described key performance indicators can be used to reduce the time required to resolve conflicts in the team, increase productivity and improve the quality of the software product.

scholarly journals Are UX Evaluation Methods Providing the Same Big Picture?

Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  
Keyword(s):  
Software Development ◽  
Decision Process ◽  
Development Process ◽  
Evaluation Methods ◽  
Sentence Completion ◽  
Software Development Process ◽  
Software Application ◽  
Software Products ◽  
Big Picture ◽  
The Impact

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.

Re-envisioning organizational complexity using a multiple perspectives model

2020 ◽  
pp. 1-17
Author(s):  
Choon Bae (Paul) Yoo
Keyword(s):  
Strategic Alliances ◽  
Business Partnerships ◽  
Multiple Perspectives ◽  
Multiple Stakeholders ◽  
Organizational Complexity ◽  
Government Organizations ◽  
Stakeholder Perspectives ◽  
Decision Making Processes ◽  
Effective Decision Making ◽  
Perspective Model

Abstract Organizations are now more complex and require collaboration to function effectively across multiple stakeholders. Consequently, they need to be familiar with collaborative projects and participate consciously in shared processes for the accomplishment of particular goals. In order to support and strengthen business partnerships, organizations could use a model based on a multi-perspective approach, as a way of visualizing effective decision-making processes and gaining an understanding regarding how they can establish and maintain stable relationships with other organizations and strategic alliances. The benefits of the new multi-perspective model could be utilized for the collaboration of multiple stakeholders and to drive future organizational change. This study presents a case study which explores the use of a multiple perspective framework in Australian Government Organizations. The results from this study suggest that a multi-perspective model may be used to address organizational complexity through the holistic integration of stakeholder perspectives and sustained knowledge flow.

Sign in / Sign up

Export Citation Format

Share Document