scholarly journals Tool of Automated System Armoured Scaffold to Rank Requirements through AHP

2019 ◽  
Vol 9 (2) ◽  
pp. 2718-2723
Keyword(s):  
Large Scale ◽  
Requirement Engineering ◽  
Fixed Number ◽  
Automated System ◽  
Priority List ◽  
Development Life Cycle ◽  
Software Firm ◽  
The Status ◽  
Software Development Life Cycle

Requirement Engineering is really significant phase in software development life cycle. Construction of software and its functionalities is entirelygrounded on the requirements elicited for the project[6]. In this paper, we propose a tool to prioritize the requirements only with AHP bearing in mind effortless implementation for large Scale Application, Precision of result and Stakeholder’s Contribution. The tool is developed in Java and SQL. This work principallyfocused on applying AHP for larger projects. The proposed framework has been assessed through an exploratory case study that has fixed number of requirements and the status after the arrival of new requirements to the priority list. This is to know about the certainty of the projected framework, which has been conducted in a software firm. Then the tool was developed for the framework and used by the company to check for the certainty of result. The deployment of the tool and the result obtained from the effort are presented.

scholarly journals Partly-Automated Scheme (PAS) Reinforced Framework to Prioritize Requirements with Abbreviated User Involvement and Verdict through AHP

2019 ◽  
Vol 9 (2) ◽  
pp. 455-462
Keyword(s):  
Large Scale ◽  
User Involvement ◽  
Requirement Engineering ◽  
Fixed Number ◽  
Priority List ◽  
Prioritization Process ◽  
Large Size ◽  
The Status ◽  
Requirement Prioritization

Extremely significant phase of SDLC is Requirement Engineering . Building of software and its functionalities successfully is exclusively based on the requirements gathered from the user of the project. The accomplishment of the end product has direct relationship with this Requirement Phase. Requirement Prioritization Process (one of the process) in the Requirement Engineering phase supports the engineers to work out and identify the prioritization among the requirements. From the available methods to prioritize the requirement, AHP is viable but not for large size projects. This work primarily concentrated on applying AHP for bigger projects. In this paper, we constructed a framework to prioritize the requirements with AHP considering Implementation Simplicity for Large Scale project, reduced number of comparisons and precise Stakeholder’s Participation. The proposed framework has been assessed through an exploratory case study that has fixed number of requirements and the status after the arrival of new requirements to the priority list. This is to know about the actuality of the proposed framework, which has been conducted in a software company. The main findings and lessons erudite from the effort are presented.

Digital Home

2014 ◽  
pp. 333-347
Author(s):  
Salamah Salamah ◽  
Massood Towhidnejad ◽  
Thomas Hilburn
Keyword(s):  
Software Engineering ◽  
Computer Science ◽  
Case Studies ◽  
Teaching Style ◽  
Object Oriented Design ◽  
Study Approach ◽  
Design And Implementation ◽  
Development Life Cycle ◽  
Software Development Life Cycle

While many Software Engineering (SE) and Computer Science (CS) textbooks make use of case studies to introduce difference concepts and methods, the case studies introduced by these texts focus on a specific life-development phase or a particular topic within software engineering object-oriented design and implementation or requirements analysis and specification. Moreover, these case studies usually do not come with instructor guidelines on how to adopt the introduced material to the instructor’s teaching style or to the particular level of the class or students in the class. The DigitalHome Case Study aims at addressing these shortcomings by providing a comprehensive set of artifacts associated with the full software development life-cycle. The project provides an extensive set of case study modules with exercises for teaching different topics in software engineering and computer science, as well as guidance for instructors on how to use these case modules. In this chapter, the authors motivate the use of the case study approach in teaching SE and CS concepts. They provide a description of the DigitalHome case study and the associated artifacts and case modules. The authors also report on the use of the developed material.

Digital Home

2017 ◽  
pp. 1284-1299
Author(s):  
Salamah Salamah ◽  
Massood Towhidnejad ◽  
Thomas Hilburn
Keyword(s):  
Software Engineering ◽  
Computer Science ◽  
Case Studies ◽  
Teaching Style ◽  
Object Oriented Design ◽  
Study Approach ◽  
Design And Implementation ◽  
Development Life Cycle ◽  
Software Development Life Cycle

While many Software Engineering (SE) and Computer Science (CS) textbooks make use of case studies to introduce difference concepts and methods, the case studies introduced by these texts focus on a specific life-development phase or a particular topic within software engineering object-oriented design and implementation or requirements analysis and specification. Moreover, these case studies usually do not come with instructor guidelines on how to adopt the introduced material to the instructor's teaching style or to the particular level of the class or students in the class. The DigitalHome Case Study aims at addressing these shortcomings by providing a comprehensive set of artifacts associated with the full software development life-cycle. The project provides an extensive set of case study modules with exercises for teaching different topics in software engineering and computer science, as well as guidance for instructors on how to use these case modules. In this chapter, the authors motivate the use of the case study approach in teaching SE and CS concepts. They provide a description of the DigitalHome case study and the associated artifacts and case modules. The authors also report on the use of the developed material.

scholarly journals Collaborative Barriers Among University - Industry - Policy (U-I-P) Entities on Environmental Matters: A Case Study in Sarawak, Malaysia

2020 ◽  
Vol 12 ◽  
pp. 316-329
Author(s):  
Janice Manyie ◽  
Geoffery James Gerusu ◽  
Roland Kueh Jui Heng
Keyword(s):  
Large Scale ◽  
Environmental Concern ◽  
Success Factor ◽  
Limited Information ◽  
Face To Face ◽  
Private Knowledge ◽  
The Status ◽  
Industry Policy ◽  
University Industry

Realizing the importance of practicing environmental concern, it is needed to understand the tools used to tackle the issues. In this study, university – industry – policy (U-I-P) entities collaboration is a significant approach that was viewed to be the success factor towards the efforts of tackling environmental issues. Collaboration work, which involves different entities benefit in a way that pushes the entities to move towards shared objectives and goals which is to improve the environmental condition. However, although the significance of U-I-P entities collaboration was known and the linkages among U-I-P entities has started, there are still limited information on the practice of collaboration specifically on the U-I-P entities linkage structures on environmental matters in Sarawak. Thus, there is a need to identify the barriers and success factor in order to develop successful collaboration. This study addressed the gap through a mixed method of qualitative and quantitative approaches which the data were collected from 199 respondents based on a face to face interview using structured questionnaires in the major divisions of Sarawak. Drawing from a large scale of study, the study explores the status of collaboration and the barriers of collaboration in Sarawak. Findings indicated that cost, private knowledge and knowledge barrier to be a major hurdle that inhibit the development of collaboration. The assessment suggested that more efforts to increase awareness on collaboration be disseminated.

Tracking antimicrobials dispensed during an anthrax attack: A case study from the New Hampshire anthrax exercise

2011 ◽  
Vol 9 (1) ◽  
pp. 65
Author(s):  
Jeanne Tropper, MS, MPH ◽  
Chris Adamski, RN, MSN ◽  
Cynthia Vinion, MEA ◽  
Sanjeeb Sapkota, MBBS, MPH
Keyword(s):  
Public Health ◽  
New Hampshire ◽  
Large Scale ◽  
Performance Metrics ◽  
Automated System ◽  
Rural Setting ◽  
Public Health Services ◽  
Public Health Response ◽  
Health Response

The Countermeasure and Response Administration (CRA) system is a Centers for Disease Control and Prevention informatics application developed to track countermeasures, including medical interventions (eg, vaccinations and pharmaceuticals) and nonmedical interventions (eg, patient isolation, quarantine, and personal protective equipment), administered during a public health response. This case study follows the use of CRA as a supplement to paper-based processes during an exercise in which antimicrobials dispensed to individual exposed persons were captured after a simulated bioterrorist attack of anthrax spores. The exercise was conducted by the New Hampshire Division of Public Health Services on April 14, 2007.Automated systems like CRA can track when medications are dispensed. The data can then be used for performance metrics, statistics, and in locating victims for follow-up study. Given that this case study was limited to a single location in a relatively rural setting, the authors concluded that more study is needed to compare the feasibility of using an automated system rather than paper-based processes for effectively managing a very large-scale urgent public health response.

BEYOND OBJECTS: OBJECTS

1992 ◽  
Vol 01 (01) ◽  
pp. 43-60 ◽  
Author(s):  
DENNIS TSICHRITZIS ◽  
OSCAR NIERSTRASZ ◽  
SIMON GIBBS
Keyword(s):  
Programming Languages ◽  
Large Scale ◽  
Software Systems ◽  
Application Development ◽  
Open Problems ◽  
Research Directions ◽  
Component Design ◽  
Development Life Cycle ◽  
Object Technology ◽  
Software Development Life Cycle

Object-orientation offers more than just objects, classes and inheritance as means to structure applications. It is an approach to application development in which software systems can be constructed by composing and refining pre-designed, plug-compatible software components. But for this approach to be successfully applied, programming languages must provide better support for component specification and software composition, the software development life-cycle must separate the issues of generic component design and reuse from that of constructing applications to meet specific requirements, and, more generally, the way we develop, manage, exchange and market software must adapt to better support large-scale reuse for software communities. In this paper we shall explore these themes and we will highlight a number of key research directions and open problems to be explored as steps towards improving the effectiveness of object technology.

scholarly journals Requirement Engineering Challenges in Agile Software Development

2021 ◽  
Vol 2021 ◽  
pp. 1-18
Author(s):  
Aqsa Rasheed ◽  
Bushra Zafar ◽  
Tehmina Shehryar ◽  
Naila Aiman Aslam ◽  
Muhammad Sajid ◽  
...  
Keyword(s):  
Software Development ◽  
Large Scale ◽  
Development Process ◽  
Requirement Engineering ◽  
Agile Software Development ◽  
Vital Role ◽  
Agile Development ◽  
Comprehensive Overview ◽  
Development Life Cycle ◽  
Agile Software

Agile software development has large success rate due to its benefits and promising nature but natively where the size of the project is small. Requirement engineering (RE) is crucial as in each software development life cycle, “Requirements” play a vital role. Though agile provides values to customer’s business needs, changing requirement, and interaction, we also have to face impediments in agile, many of which are related to requirement challenges. This article aims to find out the challenges being faced during requirement engineering of agile projects. Many research studies have been conducted on requirement challenges which are somehow biased, no suggestions are given to improve the agile development process, and the research does not highlight large-scale agile development challenges. Hence, this article covers all the challenges discussed above and presents a comprehensive overview of agile models from requirement engineering perspective. The findings and results can be very helpful for software industry to improve development process as well as for researchers who want to work further in this direction.

The Changing Structure of Opportunity: Recruitment and Careers in Large Law Firms

1983 ◽  
Vol 8 (1) ◽  
pp. 109-142 ◽  
Author(s):  
Robert L. Nelson
Keyword(s):  
Large Scale ◽  
Organizational Context ◽  
Law School ◽  
Law Firms ◽  
Service Firms ◽  
Individual Choice ◽  
The Social ◽  
The Status ◽  
Historical Periods

Growth and bureaucratization have begun to transform patterns of recruitment and career development in large law firms. Based on a case study of four large Chicago firms, this article examines these changes and their implications. The findings indicate that the social composition of large firms has become substantially more heterogeneous with respect to the status of law school attended, gender, and ethnoreligious background. However, data on lawyers' careers suggest that associates entering firms today face an increasingly bureaucratic organizational context marked by higher levels of turnover, earlier and more intensive specialization, decreased levels of client responsibility, and more frequent assignment to large-scale litigation. The article also addresses the dynamics of individual choice over type of work performed in firms. Lawyers initially working in litigation fields are far more likely to change fields of practice than are lawyers who begin in office practice fields, reflecting the increased tendency for firms to assign new associates to litigation as well as the alienating propensity of large-firm litigation for many associates. Paradoxically, a greater proportion of lawyers in traditionally organized, general service firms than in bureaucratically organized, specialty firms report that their choice of work was dictated by the firm. Also, somewhat surprisingly, the frequency with which firms explicitly direct lawyers into particular fields has not increased from earlier periods. The article concludes that these anomalies result from the fact that firms control the career choices of lawyers, and always have, but that the way such control is exercised varies across firms and historical periods.

Managing Tacit Knowledge for a Software Development Process: A Case Study

2012 ◽  
Vol 11 (01) ◽  
pp. 1250001
Author(s):  
David P. Stevens ◽  
Sonya H. Y. Hsu ◽  
Zhiwei Zhu
Keyword(s):  
Software Development ◽  
Tacit Knowledge ◽  
Development Process ◽  
Explicit Knowledge ◽  
Software Development Process ◽  
Development Life Cycle ◽  
Managerial Implications ◽  
Software Development Life Cycle ◽  
Why Questions

The acquisition and management of knowledge is increasingly more important in today's economy because of the large proportion of the workforce eligible for retirement in the next 10 years. Companies have long understood that reusing explicit knowledge in the form of policies, documentation and procedures produces tremendous savings, reduces variability, decreases costs, and improves overall quality. Unfortunately, a considerable portion of corporate knowledge is tacit or known at a non-verbal level, and does not lend itself to reuse. This research examines "how" and "why" questions regarding a specific process used for managing and sharing tacit knowledge related to the software development life cycle. The issues related to acquiring, preserving and disseminating the tacit knowledge are discussed in detail, and the advantages and managerial implications of the results of the method are described, together with implications for knowledge workers and managers in other industries.

Sign in / Sign up

Export Citation Format

Share Document