Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Rapid application system documentation
Typology: Study Guides, Projects, Research
1 / 43
This page cannot be seen from the preview
Don't miss anything!
Rapid Application Development (RAD) is a software development
methodology that focuses on building applications in a very short
amount of time; traditionally with compromises in usability, features
and/or execution speed. The term has recently become a marketing
buzzword that generically describes applications that can be designed.
Rapid application development methodology– Emphasizes
extensive user involvement in the rapid and evolutionary
construction of working prototypes of a system to accelerate the
systems development process
Prototype – A smaller-scale representation or working model of the
users’ requirements or a proposed design for an information system
…Cont’’’
planning for rapid prototyping.
For software developed planning is done by using RAD that is furnished
with all the writing of the software itself.
RAD is a lifecycle used for development of software which provides
faster development and also gives high quality software then by using
traditional software development lifecycle.
…cont’’’
RAD makes it possible to develop quality products faster, thus
valuable resources can be saved. RAD consists of the following four phases:
Requirements Planning phase
User design phase
Construction phase
Cutover phases
Outline
.NET?
What is .NET?
A set of technologies for developing and using components to
create
Web forms
We service
Windows application
Supports the software Lifecycle
Development
Debugging
Mentainance
.NET Framework structure
Compiled into the Intermediate Language (IL ), Not directly
compiled into machine code
Metadata accompanies the IL, it describes the contents of the file
(e.g.. parameters, methods…)
The Manifest describes what other components the Intermediate
Language (IL) executable needs
C# Vs .NET
CRL: It is run time environment for rapid application
The application of .NET application consists of
Classes
Namespace
Assemblies
C# application consists of
Classes
methods
...Cont’’’
When we build an application with C# the application consists of the building block
called classes
These classes collaborates with each other at run time and application gives us some
functionality
A class contains data method
Methods/ functions have behavior, the execute a code, the do things for us
CLR works like a virtual machine in executing all languages
Checking and enforcing security restrictions on the running code
Manages memory through an extremely efficient garbage collector
Conversion from IL into code native to the platform being executed
on
.NET languages are not compiled to machine code. They are
compiled to an Intermediate Language (IL).
CLR accepts the IL code and recompiles it to machine code. The
recompilation is just-in-time (JIT) meaning it is done as soon as a
function or subroutine is called.
The JIT code stays in memory for subsequent calls. In cases where
there is not enough memory it is discarded thus making JIT process
Compiling process in .NET
VB.NET VC.NET C#.NET
MSIL
(Microsoft Intermediate Language)
Unmanaged native
Code
JIT compiler
Native Code
CLR
