SCAM DA-1 SoftWare Construction
SCAM DA-1 SoftWare Construction
MAINTENANCE
SWE-2008
DIGITAL ASSIGNMENT-1
Key Features:
● Session management
● Onsite management
● Event marketing
● Reporting and event analytics
● Ticketing
● Venue management
● Registration management
● Attendee management
● We have gone through the code to prevent any kind of infinite loops and security
holes such as buffer overflow or array index overflow.
● The code is built in java, so it is organized into classes, subroutines and packages.
● We have a detailed code documentation with all the initial errors we committed
and the bugs that we have seen through.
● The code style is android style cause we are developing an android application.
● We are reusing the basic parts of a typical android application such as the Login
page, the Account details page.
● All the data is stored in database and is easy to retrieve the data.
2) Anticipating Change:
The application is frequent to updates and the API Level for apk installation will be
around 22 because most of the mobile phones these days have atleast KitKat version.
● The new features such as the BIg Data applications to predict our events in future
can also be added.
● Also our application can be added as a widget on the homescreen to reduce the
time to access the app for small event details.
● It syncs with the user’s email and gives alerts about the upcoming events.
Constructing for verification means building software in such a way that faults can be
ferreted out readily by the software engineers writing the software, as well as during
independent testing and operational activities.
Specific techniques that support constructing for verification include following coding
standards to support code reviews, unit testing, organizing code to support automated
testing, and restricted use of complex or hard-to-understand language structures, among
others.
Standards in Construction:
● Standards that directly affect construction issues include Use of external standards.
● Construction depends on the use of external standards for construction languages,
construction tools, technical interfaces, and interactions between Software
Construction and other software engineering.
● Standards come from numerous sources, including hardware and software
interface specifications such as the Object Management Group (OMG) and
international organizations such as the IEEE or ISO.
● Use of internal standards. Standards may also be created on an organizational
basis at the corporate level or for use on specific projects.
● These standards support coordination of group activities, minimizing complexity,
anticipating change, and constructing for verification.