Evolution and Maintenance of Web Sites

2011 ◽  
pp. 255-271
Author(s):  
Rafael Capilla ◽  
Juan C. Duenas
Keyword(s):  
Web Sites ◽  
Systems Development ◽  
Product Line ◽  
Software Systems ◽  
Software Products ◽  
Software Companies ◽  
Software Engineers ◽  
The Common ◽  
Common Architecture ◽  
The Web

In this chapter we describe the product line models, and show how to apply them for developing and evolving Web products. A product line captures the common and variable aspects of software systems as key assets under a common architecture. Software companies are increasingly adopting this approach in order to accelerate the development of families of similar software products. In certain domains, such as the Web systems, development and maintenance operations are required more often. New techniques to engineer Web sites are needed in order to reduce the time to market for the Web products and to maintain the systems afterward. The authors believe that understanding the notion of lightweight product line and the role that the architecture plays will help software engineers in the construction of software products, and they will be able to manage the evolution effectively against future changes.

scholarly journals Fragment-oriented programming: a framework to design and implement software product line domain components

DYNA ◽  
2018 ◽  
Vol 85 (207) ◽  
pp. 74-83 ◽  
Author(s):  
Daniel Correa ◽  
Raúl Mazo ◽  
Gloria Lucia Giraldo Goméz
Keyword(s):  
Software Product Line ◽  
Preliminary Evidence ◽  
Product Line ◽  
Software Systems ◽  
Software Components ◽  
Product Lines ◽  
Reusable Software ◽  
Software Products ◽  
Manual Intervention ◽  
Software Product

Software product lines facilitate the industrialization of software development. The main goal is to create a set of reusable software components for the rapid production of a software systems family. Many authors have proposed different approaches to design and implement the components of a product line. However, the construction and integration of these components continue to be a complex and time-consuming process. This paper introduces Fragment-oriented programming (FragOP), a framework to design and implement software product line domain components, and derive software products. FragOP is based on: (i) domain components, (ii) fragmentations points and (iii)fragments. FragOP was implemented in the VariaMos tool and using it we created a clothing stores software product line. We derivedfive different products, integrating automatically thousands of lines of code. On average, only three lines of code were manually modified;which provided preliminary evidence that using FragOP reduces manual intervention when integrating domain components.

scholarly journals Classification of digital stitch lines in machine embroidery

2021 ◽  
Vol 72 (05) ◽  
pp. 538-544
Author(s):  
DANIELA SOFRONOVA ◽  
RADOSTINA A. ANGELOVA
Keyword(s):  
Web Sites ◽  
High Tech ◽  
Apparel Design ◽  
Systematic Classification ◽  
Software Products ◽  
Software Product ◽  
Textile And Apparel ◽  
Large Application ◽  
The Web

Despite the large application of the machine embroidery in textile and apparel design and high-tech clothing items, there is а lack of systematic arrangement of the digital stitch lines, used by embroidery machines and embroidery designers. Since 2010 information on embroidery stitch lines could be mostly found in the web sites of the embroidery machine manufacturers and software product manuals. However, in the instruction manuals the instruments for creating various embroidery objects are simply described without providing systematic information on the types of the stitch lines. Even more, different names of the stitch lines and different ways to achieve the same design are observed. Single authors offer their own classifications based entirely and logically on the stitches of the hand embroidery. Another group of authors relied on already developed techniques and strategies for digitizing stitches in various software products or took into account the final appearance of the stitch lines or their application. Our study aimed to develop a detailed and systematic classification of the digital stitch lines in the machine embroidery, which has not been presented in the literature.

Customer Goals Online

2011 ◽  
pp. 163-167
Author(s):  
Thomas W. Porter
Keyword(s):  
Customer Service ◽  
Web Sites ◽  
Web Site ◽  
Traditional Approach ◽  
Product Line ◽  
Specific Product ◽  
Large Product ◽  
Apparent Reason ◽  
Goal Directed Behavior ◽  
The Web

Marketing managers charged with developing effective e-marketing strategies need to understand the implications of goal-directed behavior online. Traditionally, the marketer’s job has involved capturing the customer’s attention and communicating a message about products or services. The customer is essentially a passive receiver of the marketer’s message with little control over the marketing messages they are exposed to. Contrast the traditional approach to marketing with a Web site. Online the customer arrives at the marketer’s Web site with a goal. The customer has something that he or she wants to accomplish, whether it be to acquire information about a product, to make a purchase, or to just be entertained. By understanding the customer’s purpose for a Web site visit, the Web marketer is in a position to develop a Web site that provides significant value. Furthermore, a failure to deliver a Web site that enables customers to accomplish their goals is likely to result in dissatisfaction and defection to other more useful Web sites. Understanding customer online goals is critical because it gets at the heart of what the Web site should or could “do.” The challenge for e-marketers is that for most businesses, there are likely to be multiple goals that represent the “reason why” customers could come to the Web site. For example, an e-tailing site might be very effective for customers who already know the specific product they want to purchase. However, there are likely to be many other goals that could lead people to visit the site, such as selecting the appropriate product form a large product line, selecting an appropriate gift, or perhaps receiving customer service. If important customer goals are not supported by the Web site, the firm is at risk of losing a significant amount of business. Other times businesses compete in markets where there may be little apparent reason for a consumer to visit a Web site. As a result, and because firms feel they should have an online presence, many e-marketing sites are created that offer little more than online reproductions of the marketer’s off-line advertising. The purpose of this article is to help e-marketers better understand the nature of customer goals online so that they may be prepared to create the types of Web site experiences that provide value to their customers.

Addressing Non-Functional Properties in Feature Models: A Goal-Oriented Approach

2014 ◽  
Vol 24 (10) ◽  
pp. 1439-1487 ◽  
Author(s):  
Mehdi Noorian ◽  
Mohsen Asadi ◽  
Ebrahim Bagheri ◽  
Weichang Du
Keyword(s):  
Functional Properties ◽  
Product Line ◽  
Feature Model ◽  
Software Systems ◽  
Feature Models ◽  
Target Domain ◽  
Product Lines ◽  
Software Products ◽  
Software Product ◽  
Goal Models

Software Product Line (SPL) engineering is a systematic reuse-based software development approach which is founded on the idea of building software products using a set of core assets rather than developing individual software systems from scratch. Feature models are among the widely used artefacts for SPL development that mostly capture functional and operational variability of a system. Researchers have argued that connecting intentional variability models such as goal models with feature variability models in a target domain can enrich feature models with valuable quality and non-functional information. Interrelating goal models and feature models has already been proposed in the literature for capturing non-functional properties in software product lines; however, this manual integration process is cumbersome and tedious. In this paper, we propose a (semi) automated approach that systematically integrates feature models and goal models through standard ontologies. Our proposed approach connects feature model and goal model elements through measuring the semantic similarity of their annotated ontological concepts. Our work not only provides the means to systematically interrelate feature models and goal models but also allows domain engineers to identify and model the role and significance of non-functional properties in the domain represented by the feature model.

Customer Goals Online

2011 ◽  
pp. 1672-1678
Author(s):  
Thomas W. Porter
Keyword(s):  
Customer Service ◽  
Web Sites ◽  
Web Site ◽  
Traditional Approach ◽  
Product Line ◽  
Specific Product ◽  
Large Product ◽  
Apparent Reason ◽  
Goal Directed Behavior ◽  
The Web

Marketing managers charged with developing effective e-marketing strategies need to understand the implications of goal-directed behavior online. Traditionally, the marketer’s job has involved capturing the customer’s attention and communicating a message about products or services. The customer is essentially a passive receiver of the marketer’s message with little control over the marketing messages they are exposed to. Contrast the traditional approach to marketing with a Web site. Online the customer arrives at the marketer’s Web site with a goal. The customer has something that he or she wants to accomplish, whether it be to acquire information about a product, to make a purchase, or to just be entertained. By understanding the customer’s purpose for a Web site visit, the Web marketer is in a position to develop a Web site that provides significant value. Furthermore, a failure to deliver a Web site that enables customers to accomplish their goals is likely to result in dissatisfaction and defection to other more useful Web sites. Understanding customer online goals is critical because it gets at the heart of what the Web site should or could “do.” The challenge for e-marketers is that for most businesses, there are likely to be multiple goals that represent the “reason why” customers could come to the Web site. For example, an e-tailing site might be very effective for customers who already know the specific product they want to purchase. However, there are likely to be many other goals that could lead people to visit the site, such as selecting the appropriate product form a large product line, selecting an appropriate gift, or perhaps receiving customer service. If important customer goals are not supported by the Web site, the firm is at risk of losing a significant amount of business. Other times businesses compete in markets where there may be little apparent reason for a consumer to visit a Web site. As a result, and because firms feel they should have an online presence, many e-marketing sites are created that offer little more than online reproductions of the marketer’s off-line advertising. The purpose of this article is to help e-marketers better understand the nature of customer goals online so that they may be prepared to create the types of Web site experiences that provide value to their customers.

Process Models of SDLCs

2009 ◽  
pp. 76-89 ◽  
Author(s):  
Laura C. Rodriguez ◽  
Manuel Mora ◽  
Miguel Vargas Martin ◽  
Rory O’Connor ◽  
Francisco Alvarez
Keyword(s):  
Software Process ◽  
Systems Development ◽  
Life Cycles ◽  
Process Models ◽  
Software Systems ◽  
Engineering Discipline ◽  
Development Teams ◽  
The Common ◽  
Research Questions ◽  
Conceptual Research

The software engineering discipline has developed the concept of software process to guide development teams towards a high-quality end product to be delivered on-time and within the planned budget. Consequently,several software-systems development life-cycles (PM-SDLCs) have been theoretically formulated and empirically tested over the years. In this chapter, a conceptual research methodology is used to review the state of the art on the main PM-SDLCs formulated for software-intensive systems, with the aim to answer the following research questions: (a) What are the main characteristics that describe the PM-SDLCs?, (b) What are the common and unique characteristics of such PM-SDLCs?, and (c) What are the main benefits and limitations of PM-SDLCs from a viewpoint of a conceptual analysis? This research is motivated by a gap in the literature on comprehensive studies that describe and compare the main PMSDLCs and organizes a view of the large variety of PM-SDLCs.

A webometric analysis of major keywords and expressions in biochemistry using LexiURL Searcher

2015 ◽  
Vol 33 (6) ◽  
pp. 1163-1173 ◽  
Author(s):  
Kobra Taram ◽  
Abbas Doulani
Keyword(s):  
Web Sites ◽  
Web Site ◽  
Design Methodology ◽  
Information Access ◽  
Link Analysis ◽  
Content Type ◽  
Common Thread ◽  
The Common ◽  
Mesh Database ◽  
The Web

Purpose – The purpose of this paper is to explore webometric analysis of keywords and expressions of the biochemistry field of study via LexiURL Searcher. Design/methodology/approach – Interfaces for assisting users with information access have received considerable attention. Along with the extraction of data on Web sites for webometric purposes (e.g. link analysis, ranking of Web sites, etc.), LexiURL Searcher presents some information on the arrangement of links among different Web sites. Such capability enables users to identify one or more Web sites around their intended subject and, accordingly, explore all Web sites linked with their identified Web site(s). LexiURL Searcher has preceded webometric analysis by considering the main expressions and keywords derived from the MeSH database. Findings – The worldwide survey indicated that links from countries such as England, Japan, Germany, Australia and Canada were among the Web sites that are most used in biochemistry. Alternatively, other countries such as Singapore, Thailand and Poland had the most advantageous links to the outside world, whereas South Africa, New Zealand and The Netherlands had the least link effect. Biochemistry, being a specialized domain, would benefit greatly from site linking and would provide users the most assistance in information processing. Originality/value – Most webometric studies remain on the level of link analysis and Web site statuses; however, this paper gives information on the common thread Web sites based on a standard thesaurus.

Audience-Drive Design Approach for Web Systems

2011 ◽  
pp. 274-278 ◽  
Author(s):  
Olga De Troyer
Keyword(s):  
Web Sites ◽  
Web Applications ◽  
Web Design ◽  
Primary Factor ◽  
Software Systems ◽  
Classical Information ◽  
Business Applications ◽  
The World ◽  
The Web ◽  
Web Systems

In the last years, Web systems have evolved from a simple collection of hypertext pages toward applications supporting complex (business) applications, offering (rapidly changing) information and functionality to a highly diversified audience. Although it is still easy to publish a couple of pages, it is now recognized that appropriate Web design methods are needed to develop more complex Web sites and applications (generally called Web systems). In the past, Web systems were created opportunistically without prior planning or analysis, and without any regard for methodology, resulting in Web systems that were lacking consistency in structure, navigation, and presentation, and were not transparent. A lot of these systems were also suffering from the classical maintenance problems and development backlog. In the same period, Web technology evolved at an equally dazzling rate enabling more advanced Web applications, but with the unfavorable consequence that Web development is no longer simple and easy. The latest developments in the field of the Web are related to the vision of the Semantic Web: an extension of the current Web in which information is given well-defined meaning, better enabling computers, and people to work in cooperation (Berners-Lee, Hendler, & Lassila, 2001). Together with the Web, a new problem unknown in classical information systems emerged: competition for the visitor’s attention. Especially for commercial Web systems, it is important to hold the interest of the visitors and to keep them coming back. As stated by usability expert Nielsen (2000, p. 9), “all the competitors in the world are but a mouse click away.” Much more than in “classical” software systems, the usability of Web systems is a primary factor for their success.

MUSTER

2010 ◽  
pp. 146-165
Author(s):  
Chad Coulin ◽  
Didar Zowghi ◽  
Abd-El-Kader Sahraoui
Keyword(s):  
Systems Development ◽  
Primary Objective ◽  
Requirements Elicitation ◽  
Software Systems ◽  
Method Engineering ◽  
Group Support System ◽  
Computer Aided ◽  
Elicitation Process ◽  
The Common ◽  
Computer Aided Software Engineering

In this chapter they present a collaborative and situational tool called MUSTER, that has been specifically designed and developed for requirements elicitation workshops, and which utilizes, extends, and demonstrates a successful application of intelligent technologies for Computer Aided Software Engineering and Computer Aided Method Engineering. The primary objective of this tool is to improve the effectiveness and efficiency of the requirements elicitation process for software systems development, whilst addressing some of the common issues often encountered in practice through the integration of intelligent technologies. The tool also offers an example of how a group support system, coupled with artificial intelligence, can be applied to very practical activities and situations within the software development process.

Introduction

1994 ◽  
Author(s):  
Alan W. Brown ◽  
David J. Carney ◽  
Edwin J. Morris ◽  
Dennis B. Smith ◽  
Paul F. Zarrella
Keyword(s):  
Software Development ◽  
Computer Systems ◽  
Computer Software ◽  
Computer Hardware ◽  
Software Systems ◽  
Daily Lives ◽  
Software Products ◽  
Software Engineers ◽  
Automated Support ◽  
Reliability Performance

Computers have a significant impact on almost every aspect of our lives. Computer systems are used as integral components in the design of many of the artifacts we use and the homes we inhabit. They also control the operation of a number of devices we frequently use, and record information on many of the significant actions we take in our daily lives. The rapid increases in performance and reliability of computer hardware, coupled with dramatic decreases in their size and cost, have resulted in an explosion of uses of computer technology in a wide variety of application domains. A consequence of this trend is that computer software is in great demand. In addition to new software being written, many millions of lines of existing software are in daily use, and require constant maintenance and upgrade. As a result, computer software is very often the overriding factor in a system’s costs, reliability, performance, and usability. Software that is poorly designed, implemented, and maintained is a major problem for many companies that make use of computer systems. These facts have led to increasing attention being placed on the processes by which software is developed and maintained, and on the computer-based technology that supports these activities. Over the past decade or more, this attention has focused on understanding better how software can be produced and evolved, and on providing automated support for these processes where appropriate. One of the consequences of this attention has been the development of the field of computer-aided software engineering (CASE), which directly addresses the needs of software engineers themselves in the use of computerbased technology to support their own development and maintenance activities. The promise of CASE is that automated support for some aspects of software development and maintenance will: • increase productivity and reduce the cost of software development, • improve the quality (e.g., reliability, usability, performance) of software products, • keep documentation in step with software products as they evolve, • facilitate maintenance of existing software systems, and • make the software engineers’ task less odious and more enjoyable.

Sign in / Sign up

Export Citation Format

Share Document