Be able to design .

NET solutions
Selection
• Identification of .NET compatible programming language
• Identification of .NET programming libraries
• Selection of development environment
Identification of .NET compatible programming
language
Choosing a programming language depends on your language
experience and the scope of the application you are building
• C Sharp
• F Sharp
• J Sharp
• Visual Basic .NET
• Visual C++
Identification of .NET programming libraries
• .NET Framework applications are built on the services of the common
language runtime(CLR) and take advantage of the .NET Framework
class library(FCL).
• System
• System.Configuration
• System.Data
• System.Data.SqlClient
• System.Drawing
• System.IO
• System.Security
Selection of development environment
• Mobile
• Handheld
• Web Based
• Desktop
• Dedicated device
• server
Mobile
• Is a term used to denote the act or process by which application
software is developed for mobile devices
• Personal digital assistants
• Enterprise digital assistants
• Can be pre-installed on phones
• Delivered as web applications using server-side or client-side
processing
Handheld
• is a computer that can conveniently be stored in a pocket and used
while you're holding it
• May accept handwriting as input and those with small keyboards
• maintaining schedules
• keeping names and phone numbers
• doing simple calculations
• taking notes
• exchanging e-mail
• getting information from the Web
• Note: These all features are now available in smart phones.
Web based
• any program that is accessed over a network connection using
HTTP/HTTPS
• Web-based applications often run inside a Web browser
• Facebook
• Hotmail
• Gmail
Desktop
• Any software that can be installed on a single computer (laptop or a
desktop)
• used to perform specific tasks
• Some desktop applications can also be used by multiple users in a
networked environment
• are to be installed separately on each computer
• Good processing and performance
• Word processors
• media players
• Photoshop
Dedicated device
• Personal electronic devices that are not general purpose computers
• GPS navigation device
• Dedicated ePaper devices
• barcode reader
Server
• Applications are implemented, controlled, supported and functioned
on the server instead of the client
• Accounting Software
• core Banking System
• Enterprise Resource Planning
Systems development life cycle
• Project Initiation
• Requirement gathering and analysis
• Design
• Implementation or coding
• Testing
• Deployment
• Maintenance
Design methodology
• Reuse of existing system
• Adaptation of code
• GUI template
• Graphical interface
• Design guides
• State and interaction diagrams
• Screen layouts
• Data storage
• Event procedures and descriptions
Reuse of existing system and Adaptation of
code
• Application system reuse
• Component reuse
• Object and function reuse
GUI template
• Web Application
• Windows form
• Web Services and Clients
• NuGet Packager
• Data-Driven Dynamic MVC
Graphical interface
• Solution Explorer
• Properties Window
• ToolBox
• Error Window
• Code Window
Design Guidelines
• Use system tools whenever possible
• Maintain consistent, predictable layout & behavior and adhere to
system standards / style guides
• Provide keyboard access to all dialogs, menus, and tools
• Design software to minimize the skills and abilities needed to operate
it
• Be sure software cooperates with special access features in the OS
and third party access software
• Use an open systems approach
State and interaction diagrams
• Psuedocode
• Algorithms
• Entity Relationship diagram
• FlowChart
• Data flow diagram
• Use Case Diagram
• Gantt chart
Screen layouts

• Different Layouts based on screen resolutions

Data storage
• Database
• Text file
• Xml file
Event procedures and descriptions

• Implementation of different event based on control

• Button click
• TextBox TextChanged
Application Interaction
• Exchange of data environment
• Compliance
• Compatibility
• Recognition of standards of employed environment
Exchange of data environment

• Lets you exchange data among different types of applications

Compliance
• Application compliance is the process that determines if each
application within the application portfolio meets the compliance
policy set by the organization.
• Compliance of accounting software with vat.
Compatibility
• Application compatibility is the testing of new or upgraded
applications for OS compatibility and interoperability with other
applications
• Compatibility within Windows XP, Vista, 7, 8
Recognition of standards of employed
environment
• Recognition of standards employed n Terms of
• Memory
• Processor
• Disk Space
• Network Speed
Be able to test and document .NET solutions
Mechanisms
• Valid declarations
• Debugging code
• Comment code
• Naming conventions
• Checking functionality against requirements
• Documentation
Types of Error
• Syntax Error
• Logical Error
• Runtime Error
Software Testting
• Testing Methods
• Testing Types
Testing Methods
• Blackbox Testing
• Whitebox Testing
Blackbox Testing
• Is a testing technique that ignores the internal mechanism of the
system
• Focuses on the output generated against any input and execution of
the system
• Often used for validation
Whitebox Testing
• Is a testing technique that takes into account the internal mechanism
of a system
• Also called structural testing and glass box testing.
• Often used for verification
Types of Testing

• Unit Testing
• Integration Testing
• Functional Testing
• System Testing
• Stress Testing
• Performance Testing
• Usability Testing
• Acceptance Testing
• Regression Testing
• Beta Testing
Unit Testing
• Is the testing of an individual unit or group of related units.
• Falls under the class of white box testing.
• Often done by the programmer to test that the unit he/she has
implemented is producing expected output against given input.
Integration Testing
• Is testing in which a group of components are combined to produce
output.
• The interaction between software and hardware is tested in
integration testing if software and hardware components have any
relation.
• It may fall under both white box testing and black box testing.
Functional Testing

• Is the testing to ensure that the specified functionality required in the

system requirements works.
• It falls under the class of black box testing.
System Testing
• Is the testing to ensure that by putting the software in different
environments (e.g., Operating Systems) it still works.
• System testing is done with full system implementation and
environment.
• It falls under the class of black box testing.
Stress Testing
• Is the testing to evaluate how system behaves under unfavorable
conditions.
• Testing is conducted at beyond limits of the specifications.
• It falls under the class of black box testing.
Performance Testing
• Is the testing to assess the speed and effectiveness of the system and
to make sure it is generating results within a specified time as in
performance requirements.
• It falls under the class of black box testing.
Usability Testing
• Is performed to the perspective of the client
• To evaluate how the GUI is user-friendly?
• How easily can the client learn?
• After learning how to use
• How proficiently can the client perform?
• How pleasing is it to use its design?
• This falls under the class of black box testing.
Acceptance Testing
• Is often done by the customer to ensure that the delivered product
meets the requirements and works as the customer expected.
• It falls under the class of black box testing.
Regression Testing
• Is the testing after modification of a system, component.
• or a group of related units to ensure that the modification is working
correctly and is not damaging or imposing other modules to produce
unexpected results.
• It falls under the class of black box testing.
Beta Testing
• Is the testing which is done by
• end users
• a team outside development
• Publicly releasing full pre-version of the product which is known as
beta version.
• The aim of beta testing is to cover unexpected errors.
• It falls under the class of black box testing.
Feedback
• Record feedback
• Surveys
• Questionnaire
• Interviews
• Analyze feedback
• Present results
Documentation
• User
• Onscreen help to assist users of the programme
• Pop-ups
• Help menu
• hot-spots
Documentation
• Technical
• Designs
• Delivery system
• Platform
• Environment
• File structures
• Coding
• Constraints
• Documentation for maintenance of programme
• Installation
• Backup
• Restore
• Upgrade