Untitled

Ramesh, Balasubramaniam; Pries‐Heje, Jan; Baskerville, Richard

doi:10.1023/a:1020557725165

Cited by 31 publications

(4 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Depending on the category of a Web Application, different resources, techniques and methods are required to develop them. Also, the purpose of Web Applications can change with the category [2,9]. The complexity of each new category is growing.…”

Section: Categorization Of Web Applicationsmentioning

confidence: 99%

Development of ISIRS Web Application Using Object Behavioral Modeling

Abdul-Nabi

2010

Jour. Kufa Math. Comp.

View full text Add to dashboard Cite

The growth of the Internet and the World Wide Web (WWW) has resulted in a largenumber of Web Systems and Web Applications. Today many people are relying on Web applications like Internet banking, entertainment and E-commerce applications. They expect these applications to be available, safe, secure and reliable. In this research, the purpose is to give an understanding of the special characteristics of Web Applications and the Web Engineering process used to develop these applications. We first analyze the current state of the art of Web applications design, stating the need for an approach that clearly separates concerns (conceptual, navigational, interface). Briefly introduce the ISIRS (Instructors and Students Information & Registration System) application as an object behavioral model of Web applications design. Keywords: Web Engineering, Software Engineering, Web Engineering Process, Web application development.

show abstract

Section: Categorization Of Web Applicationsmentioning

confidence: 99%

Development of ISIRS Web Application Using Object Behavioral Modeling

Abdul-Nabi

2010

Jour. Kufa Math. Comp.

View full text Add to dashboard Cite

show abstract

“…The development of Web-based systems is often distinctly different from the development of traditional Information Technology (IT) systems, as Web-based applications are typically much smaller than traditional IT applications and, consequently, their production period is much shorter (Cusumano & Yoffie, 1999;Iansiti & MacCormack, 1997;Kirda, Jazayeri, Kerer, & Schranz, 2001;Ramesh, Pries-Heje, & Baskerville, 2002). Furthermore, these applications evolve at a much faster pace, and the development cycle is highly iterative in nature.…”

Section: Introductionmentioning

confidence: 99%

“…Furthermore, these applications evolve at a much faster pace, and the development cycle is highly iterative in nature. Due to these factors, agile development methodologies are increasingly being used for the development of Web-based applications (Barnett & Narsu, 2005;Ramesh, Pries-Heje, & Baskerville, 2002). Until recently, agile development methodologies and traditional security engineering have been seen as orthogonal (Beznosov & Kruchten, 2004); however, recent discussions are beginning to harmonize the two seemingly different viewpoints (Beznosov, 2003;Beznosov & Kruchten, 2004).…”

Section: Introductionmentioning

confidence: 99%

Agile Development of Secure Web-Based Applications

Tappenden

Huynh

Miller

et al. 2006

International Journal of Information Technology and Web Engineering

View full text Add to dashboard Cite

This article outlines a four-point strategy for the development of secure Web-based applications within an agile development framework and introduces strategies to mitigate security risks commonly present in Web-based applications. The proposed strategy includes the representation of security requirements as test cases supported by the open source tool FIT, the deployment of a highly testable architecture allowing for security testing of the application at all levels, the outlining of an extensive security testing strategy supported by the open source unit-testing framework HTTPUnit, and the introduction of the novel technique of security refactoring that transforms insecure working code into a functionally equivalent secure code. Today, many Web-based applications are not secure, and limited literature exists concerning the use of agile methods within this domain. It is the intention of this article to further discussions and research regarding the use of an agile methodology for the development of secure Web-based applications.

show abstract

“…This form of development was named short cycle time development after a series of studies of commercial Internet software development in small niche companies identified a recurring group of five characteristic practices (Baskerville, Levine, Pries-Heje, Ramash, & Slaughter, 2001;Baskerville & Pries-Heje, 2004;Ramesh, Pries-Heje, & Baskerville, 2002). These practices include a focus on completion speed, release-oriented parallel development with prototyping, the criticality of architecture, negotiable product quality, and an ideal workforce.…”

Section: Spontaneously Occurring Agile Approachesmentioning

confidence: 99%

A Theory of Coordination in Agile Software Development Projects

Strode¹

View full text Add to dashboard Cite

<p>Agile software development offers a deceptively simple means to organise complex multi-participant software development while achieving fast delivery of quality software, meeting customer requirements, and coping effectively with project change. There is little understanding, however, of how agile software development projects achieve effective coordination, a critical factor in successful software projects. Agile software development provides a unique set of practices for organising the work of software projects, and these practices seem to achieve effective project coordination. Therefore, this thesis takes a coordination perspective to explore how agile software projects work, and why they are effective. The outcome of this research is a theory of coordination in co-located agile software development projects. To build a coordination theory, evidence was drawn from a multi-case study following the positivist tradition in information systems. Three cases of agile software development contributed to the theory, along with one additional non-agile project that contributed contrasting evidence. The findings show that agile software development practices form a coordination strategy addressing three broad categories of dependency: knowledge dependencies, task dependencies, and resource dependencies. Most coordination is for managing requirement, expertise, historical, and task allocation dependencies; all forms of knowledge dependency. Also present are task dependencies, which include activity or business process dependencies, and resource dependencies, which include technical or entity dependencies. The theory of coordination explains that an agile coordination strategy consists of coordination mechanisms for synchronising the project team, for structuring their relations, and for boundary spanning. A coordination strategy contributes to coordination effectiveness, which has explicit and implicit components. The primary contribution of this theory is an explanation of how agile software development practices act together to achieve effective project coordination. The coordination strategy concept can be used to select practices from agile methods to ensure software projects achieve effective coordination. In addition, once operationalised in future work, the well-grounded theoretical concepts developed in this research will provide valuable tools for measuring the coordination effectiveness of agile method adoption and adaptation.</p>

show abstract

Untitled

Cited by 31 publications

References 24 publications

Development of ISIRS Web Application Using Object Behavioral Modeling

Development of ISIRS Web Application Using Object Behavioral Modeling

Agile Development of Secure Web-Based Applications

A Theory of Coordination in Agile Software Development Projects

Contact Info

Product

Resources

About