Scribd
Upload
15 views3 pages

Unit 4

Uploaded by

thanusunkara8
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
15 views3 pages

Unit 4

Uploaded by

thanusunkara8
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

An overview of interface specification:

Interface specification is a standardized mechanism that allows different subsystems to


communicate and operate as independent modules in software engineering .

An interface is a point where two systems, subjects, organizations, etc.


meet and interact. In computing, an interface is a shared boundary
across which two or more separate components of a computer system
exchange information. The exchange can be between software, computer
hardware, peripheral devices, humans or combinations of these. We can
therefore see that there are several types of interface which we might be
interested in:
•
User interface, where the user interacts with the software.
•
Hardware interface, where electronic components interact.
•
Software interface, where software components, including
operating systems, interact.
•
Systems interface, where software systems interact in order to pass
information (synchronization and interrogation).
Here are some things to consider about interface specifications:
 User interface (UI) specifications: These documents are the main source of
implementation information for how software should work. They should also consider
usability, localization, and demo limits. UI specifications can be used by marketing,
graphic design, and software testing teams.
 Interface requirements specifications (IRS): These documents specify requirements
for a given external interface.
 Interface design descriptions (IDD): These documents are used when an IRS doesn't
specify all the details needed to fabricate or code the interface.
 Interface control documents (ICD): These documents are another name for interface
specifications.
 Interface management: This is needed to ensure that interface requirements are
created consistently.
 External interfaces: These are the interfaces that a software application has with its
environment. There are two types of external interfaces: logical interfaces (software-
software) and physical interfaces (software-hardware).
State of the Art:

Model-based Software Engineering

• During object design we build an object design model that realizes the use case model and it is the
basis for implementation (model-driven design)

• The Reality

• Working on the object design model involves many activities that are error prone

• Examples: • A new parameter must be added to an operation. Because of time pressure it is


added to the source code, but not to the object model

• Additional attributes are added to an entity object, but the database table is not updated (as a
result, the new attributes are not persistent).

Other Object Design Activities

• Programming languages do not support the concept of a UML association

• The associations of the object model must be transformed into collections of object references

• Many programming languages do not support contracts (invariants, pre and post conditions)

• Developers must therefore manually transform contract specification into source code for
detecting and handling contract violations

• The client changes the requirements during object design

• The developer must change the interface specification of the involved classes

• All these object design activities cause problems, because they need to be done manually.

• Let us get a handle on these problems

• To do this we distinguish two kinds of spaces

• the model space and the source code space

4 different types of transformations

• Model transformation,

• Forward engineering,

• Reverse engineering,

• Refactoring.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy