Search the World's Largest Database of Information Science & Technology Terms & Definitions
InfInfoScipedia LogoScipedia
A Free Service of IGI Global Publishing House
Below please find a list of definitions for the term that
you selected from multiple scholarly research resources.

What is Software component

Software Engineering for Agile Application Development
A software unit of functionality that manages a single abstraction.
Published in Chapter:
Product Backlog and Requirements Engineering for Enterprise Application Development
Chung-Yeung Pang (Seveco AG, Switzerland)
Copyright: © 2020 |Pages: 29
DOI: 10.4018/978-1-7998-2531-9.ch001
Abstract
The combination of software engineering and agile development process can bring great benefits to the development and maintenance of enterprise applications. This chapter introduces the engineering of requirements in an agile Scrum development process. In Scrum, requirements are usually defined as user stories in a product backlog. Since many enterprise applications do not have intensive user actions, stories cannot be linked to users. Topics such as user and enabler stories, non-functional requirements, considerations of architecture and business components, business workflow, and breakdown of user stories are addressed. The requirements engineering of PBIs is illustrated by practical examples. Using UML use cases and collaboration models is recommended to transform the stories in the product backlog into formal requirements specifications. The proposed approach can be part of the agile development framework for flexible software products that are easy to customize and maintain.
Full Text Chapter Download: US $37.50 Add to Cart
More Results
An Agent and Pattern-Oriented Approach to Data Visualization
A software unit of functionality that manages a single abstraction.
Full Text Chapter Download: US $37.50 Add to Cart
Supporting Data-Intensive Analysis Processes: A Review of Enabling Technologies and Trends
Modern software applications and systems are most often developed as assemblies of many smaller parts. The idea of software components formalizes the definition of these “smaller parts”: A software component is basically a software unit with a well-defined interface and explicitly specified dependencies. A software component can be as small as a block of reusable code, or it can be as big as an entire application.
Full Text Chapter Download: US $37.50 Add to Cart
Full Text Chapter Download: US $37.50 Add to Cart
New Technologies in Hospital Information Systems
A system element offering a predefined service and able to communicate with other components.
Full Text Chapter Download: US $37.50 Add to Cart
Reuse in Agile Development Process
A software unit of functionality that manages a single abstraction.
Full Text Chapter Download: US $37.50 Add to Cart
Overlay-Based Middleware for the Pervasive Grid
A third party deployable software module that has private data and a set of provided and required interfaces that explicitly describe the component’s behaviour.
Full Text Chapter Download: US $37.50 Add to Cart
Applying Software Engineering Design Principles to Agile Architecture
A software unit of functionality that manages a single abstraction.
Full Text Chapter Download: US $37.50 Add to Cart
A Reference Architecture for Game-Based Intelligent Tutoring
Reusable software part that can be easily plugged together with other components to form a software application.
Full Text Chapter Download: US $37.50 Add to Cart
eContent Pro Discount Banner
InfoSci OnDemandECP Editorial ServicesAGOSR