Integrating Tagging Software in Web Application

2018 ◽  
pp. 46-67
Author(s):  
Karan Gupta ◽  
Anita Goel
Keyword(s):  
Web Application ◽  
Web Applications ◽  
Design Phase ◽  
Design Document ◽  
Software Estimation ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Logical Design

Tag software is included in web applications to facilitate categorization and classification of information. Generally, freely available tag software is adapted or new code written to incorporate tagging. However, there is an absence of requirement and design document for tagging, even academically. It becomes difficult to know the features that can be included in tag software; also, not all features may be required. This chapter presents a framework for integration of tag software in web applications. The framework has four components corresponding to phases of the software development lifecycle. For requirement, a weighted requirement checklist is presented to ease requirement selection. A metric, software estimation, is defined for quantifying selected requirement. A logical design defined for design phase displays interaction of entities with users. For development, best mechanisms are suggested to web applications. Software engineering artefacts are provided to help during testing. A case study is presented where estimation and design is applied to freely available tag software.

Requirement Estimation and Design of Tag software in Web Application

2014 ◽  
Vol 9 (2) ◽  
pp. 1-19 ◽  
Author(s):  
Karan Gupta ◽  
Anita Goel
Keyword(s):  
Decision Process ◽  
Web Application ◽  
Design Document ◽  
Requirement Specification ◽  
Software Estimation

Tag software is included in a web application to facilitate categorization and classification of information. Generally, freely available tag software is adapted, or new code is written to incorporate tagging functionality. Since there is an absence of requirement specification and design document for tag software, even academically, it becomes difficult for the user to know about the possible features that can be included in the tag software. The user has to search for those features to be able to implement them in the software. So, there is a need that the user is made aware of the features available. Moreover, not all the features are relevant for the user; hence, there is a need for some kind of mechanism to ease the decision process. This paper presents - (1) a design for tag software, and (2) categorization of requirements of tag software in a web application. The design helps the developer during updating and analysis. The logical view of design displays interaction of entities and sub-entities with users. A weighted requirement checklist is presented which segregates features in three categories based on their popularity. This eases the task of selecting the requirement of tag software for the user. A metric, software estimation, is defined for quantifying selected requirements. A case study of freely available tag software is presented, in which estimation and design is applied.

scholarly journals A Secure Software Specification Development Strategy for Enterprises : A Case Study Approach

2021 ◽  
pp. 260-266
Author(s):  
Sifat Ali Sathio ◽  
Isma Farah Siddiqui ◽  
Qasim Ali Arain
Keyword(s):  
Software Development ◽  
Web Application ◽  
Assessment Model ◽  
Case Study Approach ◽  
Software Specification ◽  
Study Approach ◽  
Development Lifecycle ◽  
Secure Software ◽  
Software Development Lifecycle

Although Security is a non-functional requirement, it is a very essential requirement for software systems, to achieve secure software specification development for enterprises we need to find and fix vulnerabilities in the early phase of SDLC. For the successful achievement of secure software specification development in the software enterprise, the security of software application plays a very vital role. During the software development lifecycle, improper security can lead to thoughtful and serious consequences in any enterprise. In this paper, the case study approach is followed regarding the achievement of a secure web application, finding and fixing vulnerabilities in the early software development lifecycle, and applying the re-engineering process on a developed web application using the best security assessment model considering the literature review. Also, validation of the developed application is done with the help of Penetration testing.

Agile Software Development

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

Applying the WDP Technique to Usability Inspections in Web Development Organizations

2010 ◽  
pp. 324-344 ◽  
Author(s):  
Tayana Conte ◽  
Verônica T. Vaz ◽  
Jobson Massolar ◽  
Andrew Bott ◽  
Emilia Mendes ◽  
...  
Keyword(s):  
Web Application ◽  
Web Applications ◽  
Evaluation Method ◽  
Web Design ◽  
Usability Evaluation ◽  
Heuristic Evaluation ◽  
Web Development ◽  
Industrial Case Study ◽  
Development Organizations

This chapter presents the WDP (Web Design Perspectives-based Usability Evaluation), an inspection technique specifically designed to assess the usability of Web applications. This technique combines Web design perspectives and the heuristic evaluation method proposed by Nielsen (1994b). In addition to describing the components of the WDP technique this chapter also illustrates its use in practice by means of an industrial case study where the technique is applied to inspect a real Web application. In this case study, developers and requirement assessment staff applied the WDP technique to evaluate the usability of modules developed from scratch for a Web application. The results of this case study indicate the feasibility of performing usability inspections with the participation of a software project’s stakeholders, even when stakeholders are not usability experts.

scholarly journals Weighted Visibility Classification and Seating Plan for the Aitken University Centre

2014 ◽  
Vol XL-2 ◽  
pp. 227-234
Author(s):  
T. Allison ◽  
D. Fraser ◽  
E. Stefanakis
Keyword(s):  
Web Application ◽  
Web Applications ◽  
Ice Surface ◽  
Price Levels ◽  
Digital Elevation ◽  
Information Products ◽  
Interactive Map ◽  
Elevation Model ◽  
The University

This paper describes the requirements for a weighted visibility classification of seats in the University of New Brunswick’s (UNB) Aitken University Centre (AUC). Price levels for seats are typically set for sections of seats based on promoter preferences. In a visibility classification, the digital elevation model (DEM) is created for the AUC and includes possible view obstructions. The view obstructions taken into account for this design were the penalty boxes, player bencher, and the rink boards. There were no other major obstructions in the AUC. The visibility calculations compute the number of visible pixels of the rink surface for each seat. It is expected that seats with a higher number of visible pixels will also have better visibility. The number of viewable pixels is weighted by distance to the center of ice surface to account for the preference of seats that are closer to the rink surface. This paper outlines the collection of data, weighted visibility classification method, and the development of information products. There are two main objectives of this weighted visibility classification and seating plan: (a) to demonstrate that a weighted visibility classification is a viable method to classify seats, and that this methodology could be used to set price levels for a venue and (b) create online web applications to suit the functionality for users and venue administrators. The user web application allows the user to pan, zoom and perform limited searches in the interactive map.

scholarly journals ENHANCED ONLINE BOOK STORE MODEL: ADOPTING THE PROGRESSIVE WEB APPLICATION (PWA) TECHNOLOGY

2020 ◽  
Vol 9 (9) ◽  
pp. 1-8
Keyword(s):  
Web Application ◽  
Web Applications ◽  
Research Work ◽  
Business Owners ◽  
Proposed Model ◽  
Book Store ◽  
Architectural Framework ◽  
Mobile Development ◽  
Online Book

From the physical book store to the online bookstore, business owners find a way to meet the demands of their prospective customers. The daily advancement in technology has brought about a huge change the operation of e-commerce. The development of the Progressive Web Applications (PWA) by Google has caused a revolution in mobile development. Using an online bookstore as a case study, this research work presents a PWA architectural framework that can be adopted by any e-commerce applications. This was achieved after a systematic review of existing online bookstore models was carried out – identifying the gaps which will serve as strengths for the proposed model. Also, the emerging technology of PWA was critically reviewed to solidify the proposed model. Adoption of the model will avoid current issues faced the world of mobile development especially code fragmentation. However, exploring the payment gateways and modules will help solidify the model.

On the Prospects and Concerns of Pattern-Oriented Web Engineering

2010 ◽  
pp. 97-128
Author(s):  
Pankaj Kamthan
Keyword(s):  
Web Application ◽  
Process Model ◽  
Web Applications ◽  
Future Research ◽  
Design Phase ◽  
Quality Model ◽  
Web Engineering ◽  
Support Decision Making ◽  
Development And Evolution ◽  
Selection Of

In this chapter, the development and evolution of Web Applications is viewed from an engineering perspective that relies on and accommodates the knowledge inherent in patterns. It proposes an approach in the direction of building a foundation for pattern-oriented Web Engineering. For that, a methodology for pattern-oriented Web Engineering, namely POWEM, is described. The steps of POWEM include selection of a suitable development process model, construction of a semiotic quality model, namely PoQ, and selection and mapping of suitable patterns to quality attributes in PoQ. To support decision making and to place POWEM in context, the feasibility issues involved in each step are discussed. For the sake of is illustration, the use of patterns during the design phase of a Web Application are highlighted. Finally, some directions for future research, including those for Web Engineering education and Social Web Applications, are given.

Measuring Security

2021 ◽  
pp. 1303-1330
Author(s):  
Shruti Jaiswal ◽  
Daya Gupta
Keyword(s):  
Software Development ◽  
Security Requirements ◽  
Clear Understanding ◽  
Security Testing ◽  
Security Issues ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Security Algorithm ◽  
Environment Parameters

The researchers have been focusing on embedding security from the early phases of software development lifecycle. They have researched and innovated a field of Security Engineering where security concerns are embedded during requirement, design, and testing phases of software development. Efforts were made in developing methods, methodologies, and tools to handle security issues. Various methods are present in the literature for eliciting, analyzing and prioritizing the security requirements. During the design phase based on prioritized requirements, environment parameters and attribute a suitable security algorithm mainly cryptography algorithms are identified. Then a question arises how to test the effectiveness of chosen algorithm? Therefore, as an answer to the issue in this paper, a process for Security Testing is presented that evaluates the selected security algorithms. Evaluation is done by generating the test scenarios for functionalities using sequence diagram representing the threats at vulnerable points. Then, checking the mitigation of potential threats at identified vulnerable points. A security index is generated which shows the effectiveness of deployed/ chosen security algorithm. The process ends with the generation of a test report depicting the testing summary. For a clear understanding of the process, the proposal is illustrated with a case study of the cloud storage as a service model.

Analysis and Classification of Requirements Specification for Web Application Development: A Case Study Approach

2020 ◽  
Vol 27 (1) ◽  
Author(s):  
IP Gambo ◽  
HO Odukoy ◽  
AA Oke ◽  
ER Adagunodo
Keyword(s):  
Web Application ◽  
Quantitative Research ◽  
Unified Modeling Language ◽  
Application Development ◽  
Unified Modeling ◽  
Study Approach ◽  
Web Application Development ◽  
Requirement Prioritization

In this paper, we formulated, designed, implemented and evaluated a model used for classifying stakeholders' requirements that are specified for web application development. The study employed both qualitative and quantitative research approaches in a case study. Requirements were elicited from stakeholders using the interview approach. This involved speaking with the stakeholders directly via groupware and asking them questions about their specific needs that are relevant to the development of web application. In particular, 10 customers of Procrea8 Technology Solution Limited and 9 developers were used as respondents. An interactive genetic algorithm was used to formulate the model. The design was specified using the Unified Modeling Language (UML) tool, and implemented using specified web technology tools. The model was evaluated for completeness and consistency using recall and precision as parameters. The results showed that a list of ordered requirements was produced based on the stakeholders' priorities inputted into the model. The output indicated the order of priorities finally assigned to each of the requirements. The evaluation revealed that the model is effective, efficient, userfriendly, reliable (with 96.3% accuracy), scalable (prioritized over 500 requirements), less timeconsuming (prioritizing over 500 requirements) and able to update ranks whenever changes occur automatically. Also, the model evaluation indicates 97.1% precision (consistency), and 96.0% recall (completeness). The study shows that requirements engineers could use the model to collate stakeholders’ requirements from wide geographical locations. Keywords: Requirements analysis, requirement prioritization, requirements engineering, web application, requirement specification.

scholarly journals Learning from the Case Studies, How Global Software Development Process is executed in an Agile Method Environment

2010 ◽  
Vol 1 (2) ◽  
Author(s):  
Ridi Ferdiana ◽  
Lukito Edi Nugroho ◽  
Paulus Insap Santoso ◽  
Ahmad Ashari
Keyword(s):  
Software Development ◽  
Extreme Programming ◽  
Global Software Development ◽  
Agile Methods ◽  
Analysis Method ◽  
Agile Method ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Unified Process

Abstrak. Belajar dari Studi Kasus, Bagaimana Proses Pengembangan Perangkat Lunak Global Dieksekusi Pada Lingkungan Metode Agile. Tantangan terbesar dalam Software Development Global (GSD) adalah efisiensi waktu untuk mengembangkan. GSD menyediakan panduan untuk menggunakan proses bersama dengan muka seperti proses metode analisis terpadu atau metode air terjun. Meskipun, itu memberikan manfaat melalui dokumentasi yang komprehensif dan kejelasan, ia memberikan menghambat organisasi yang ingin menggunakan GSD tetapi dalam terburu-buru. Metode Agile mengklaim efisien dan pendekatan yang efektif untuk pengembangan perangkat lunak. Makalah ini laporan tentang bagaimana organisasi menggabungkan proses GSD dengan metode tangkas seperti eXtreme Programming (XP), Scrum, Agile Unified Process (UP Agile), Pengembangan Fitur Driven (FDD), dan Microsoft Solusi Kerangka Agile (MSF Agile). Makalah ini menggunakan studi kasus untuk mendapatkan pengalaman organisasi dan menjelaskan praktek yang berguna untuk organisasi yang ingin menerapkan GSD dengan metode tangkas. Kata Kunci: Siklus Hidup Pengembangan Perangkat Lunak, Agile, GSD Abstract. The biggest challenge in Global Software Development (GSD) is the efficiency of time to develop. GSD provides a guidance to use the process along with up-front analysis method like unified process or waterfall method. Although, it gives a benefit through comprehensive documentation and its clearness, it gives inhibits the organization which wants use GSD but in a rush. Agile methods claim an efficient and the effective approach to software development. This paper reports on how organizations combine the GSD process with agile methods like eXtreme Programming (XP), Scrum, Agile Unified Process (Agile UP), Feature Driven Development (FDD), and Microsoft Solution Framework Agile (MSF Agile). The paper uses case study to get organization experiences and describe useful practices for the organization that want to implement GSD with an agile method. Keywords: Software Development Lifecycle, Agile, GSD

Sign in / Sign up

Export Citation Format

Share Document