qwertyuiopasdfghjklzxcvbnmqwerty

uiopasdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfghjklzx
cvbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopasdfg
hjklzxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopasdfg
hjklzxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopasdfg
hjklzxcvbnmrtyuiopasdfghjklzxcvbn
mqwertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyuiopas
dfghjklzxcvbnmqwertyuiopasdfghjklz



Windows Services










2 | P a g e

Table of Contents
Introduction ...................................................................................................................................... 2
Windows services .............................................................................................................................. 4
Cube service controller engine .......................................................................................................... 5
Classes under the cube service .......................................................................................................... 6
Mail, person, proxy, services and settings-1000 ............................................................................. 6
Tester project with an XML file-700 ................................................................................................. 10
Testing Phase .................................................................................................................................. 19
Objective and Goals ..................................................................................................................... 20
Objectives ................................................................................................................................ 20
Goals ....................................................................................................................................... 20
Deliverables and approvals .......................................................................................................... 21
Recommendation ............................................................................................................................ 24
Conclusion ....................................................................................................................................... 27
References ...................................................................................................................................... 28










3 | P a g e

Introduction
The oldest of all Microsofts operating systems is MS-DOS (Microsoft Disk Operating
System). MS-DOS is a text-based operating system. Users have to type commands slightly
when they need to use the graphical user interfaces (GUIs). Despite its very basic
appearance, MS-DOS is a very powerful operating system. There are many advanced
applications and games available for MS-DOS. A version of MS-DOS underpins Windows.
Many advanced administration tasks in Windows can only be performed using MS-DOS. The
history of Microsoft Windows dates back to 1985, when Microsoft released Microsoft
Windows Version 1.01. Microsofts aim was to provide a friendly user-interface known as a
GUI (graphical user interface) which allowed for easier navigation of the system features.
Windows 1.01 never really caught on. In 1987 Microsoft revamped the operating system and
released Windows 2.03. The GUI was very slightly improved but still looked too similar to
Windows 1.01. The operating system again failed to capture a wide audience. Microsoft
made an enormous impression with Windows 3.0 and 3.1. Graphics and functionality were
drastically improved. The Windows 3.x family provided multimedia capabilities as well as
vastly improved graphics and application support. Building on the success of Windows 3.x,
Microsoft released Microsoft Windows for Workgroups 3.11. This gave Windows the ability
to function on a network. It is not uncommon to find companies still using Windows 3.11. In
1993 Microsoft divided the operating system into two categories; Business and home user.
Windows NT (New Technology) was a lot more reliable than Windows 3.x. Windows NT
provided advanced network features. On the business front, Windows NT continued to
develop with the release of version 3.51. Different versions were provided which offered
different functionality. Server provided the higher network functions and Workstation was
mainly for the client machines (Barber, 2005). In 1995 Windows went through a major
revamp and Microsoft Windows 95 was released. This provided greatly improved multimedia
and a much more polished user interface. The now familiar desktop and Start Menu appeared.
Internet and networking support was built in although Windows 95 was a home user
operating system, it proved to be very popular in schools and businesses. After the success of
Windows 95, Microsoft improved the GUI interface of Windows NT and released Windows
NT 4.0. NT4 could be tailored to the size of the business, NT4 Server for small to medium
sized businesses and Enterprise Server for larger networks. Microsoft continued to improve
the Windows format. Although Microsoft Windows 98 was very similar to Windows 95, it
offered a much tidier display and enhanced multimedia support. Breaking with its
own naming conventions, Microsoft released Windows 2000 for the business market. It

4 | P a g e

appeared in 4 models: Professional which replaced Workstation, Server, Advanced Server
and Data enter Server catered for differing business requirements.
Windows services
Microsoft windows service is also known as NT services, and it enables us to invent long
term executable applications which generally run in the particular Windows sessions. These
particular services can be automatically started when the computer starts, or it can be paused
and reboot, and at that time it will never display the user interface. These windows quality
creates the services ideal for using the server or whenever at we need it for the long-term
functionality which never interferes with the other users who are working on the same
desktop. We can also run the services in the security context of the particular user accounts
which is always different from the other user or the default desktop account. To get more
information about the windows services and Windows sessions we can verify the SDK
documents located in the MSDN Library (Becker, 2012). Therefore, we can also create
services by inventing an application which will be installed as a service. For instance- assume
that we want good performance by the monitor counter data and need to react upon the
values, then for that purpose we have to write a windows service application which will
justify the performance counter data, deploy the application, and then it will start analyzing
and collecting data. Therefore, the commands that will be sent for the service includes
starting, pausing, resuming and stopping the services, we can also execute custom demands.
At the time when the application is build and created then we can easily install it by running
the command-line utility InstallUtil.exe and passing the path to the executable file of the
service. Then we can also use the Services control manager to start, pause, resume or stop the
services. We will also be able to achieve these particular tasks in the services node in Server
explorer or by using the Service controller class. Windows service applications run in their
own security context and are started before the user logs into the Windows computer on
which they are installed. You should plan carefully what user account to run the service
within; a service running under the system account has more permissions and privileges than
a user account. The chief method for the service application is that it should always issue the
Run command for the particular services of the project. Therefore, the Run method loads the
services into the Services control manager on the same server. If any person uses these
Windows services then it will be automatically written by this particular method. Generally
there are two types of services available in the Windows service controller. The very first

5 | P a g e

service is the Win32OwnProcess and the other is Win32shareProcess. Therefore, the service
controller component is utilized to connect with an installed service and control its state by
using the service Controller component we can also start and stop the service. In fact, in most
of the cases the Service Controller Services the applications should be separated from the
application of the windows services which clearly define the service.
Cube service controller engine
All the reporting services are best technique to offer the formatting and the processing of the
data that are found in huge variety and at the same time interacts with the formats of different
reports. The service controller engine is one of the best xml and cube services that can be
easily provided in the visual studio section with the help of the softwares and other
demanding network protocol. This is undoubtedly one of the best process that can
interchange all the coding process and the other dilemmas that are affectively used in the
functions that are also used in the class function that is derived above. This is also the best
technique by the using the above secured steps we can easily figure out that solutions that are
wanted in the above coding of the visual network system. The controller engine system helps
the entire system to develop such a technique that is quite helpful and at the same time
initiates the entire programming process for the system. The relationship model helps the
entire data ware house to contain all the reports that are in a report format and extracts all the
data that are from team projects and are easily defined in all the projects that are collected
from the above software (Berg, 1996). This is the best process and technique to be served in
the visual basic software that adds up to the network and at the same helps the programs to be
quite effective and at the same time helps the entire system to pass through the window
services that are quite effectively based and help the user to retain the desired output that
helps to access the entire file. The cube service controller engine is one of the finest systems
that allows the users to concentrate on the program that is provided in the visual environment
and in the interface that helps all the mail services, and settings that also allows the persons
and the proxy network to render all the mailing facilities that are available in the current
network for the formation of a effective system design for the programmer and for the
techniques that helps the programmer to figure out all then required assumption that are made
for the benefit of the entire system and also makes sure that the program does not have any
errors. The service controller system has several debug and configuration files that help the
exe files to run into the system so that it does not affects the file any longer and figures out

6 | P a g e

the results in a much effective manner. This is by far the most formidable process that also
allows the programmer to go through the files much effectively. The system administrator
also helps the entire process to a great extent as it performs numerous trail and hit method in
all respect to make sure that all the system equipments are at places and moves towards the
programs with all round activities that enables the user to use the system much more
effectively and without any syntactical error for the user that are using the cube controller for
the very first time and allows the system to go through a booting phase. The user control
system helps the entire coding system to move on to next direction and follow all the
mandatory steps and solutions that are provided in the system by the user and by the coding
system of the entire design that helps the user to obtain the desired result in a quick
succession without any hesitation. The user must follow all the rules, terms and conditions
that are stated in the coding system and at the same time helps the code to generate all the
classes that are under the cube services such as cube, person, proxy, settings and many other
sub classes that fall under the class function.
Classes under the cube service
Mail, person, proxy, services and settings-1000
There are several classes that are under the cube service controller such as the mail services,
the proxy services and the personal settings that are required for the windows services. These
are the main points that are important for the entire structure to have a demanding effect on
the coding structures that are important for visual studio which have a great importance on
the structural coding of all the structures that are mentioned above and below in the coding
structures. All the above mentioned classes and functions are quite important for the entire
coding structure and are divided into different parts of coding that can be found in the
structures below.
CUBE#show run
Building configuration...
Current configuration : 5888 bytes
Last configuration change at 13:16:50 CDT Mon Feb 11 2008
NVRAM config last updated at 13:24:35 CDT Mon Feb 11 2008

7 | P a g e

version 12.4
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
service password-encryption
hostname CUBE
boot-start-marker
boot system flash:c2800nm-ipvoice_ivs-mz.124-18.2.2.PIA1p.bin
boot-end-marker
logging message-counter syslog
logging buffered 2000000
no logging console
no logging monitor
enable lab 0
no aaa new-model
memory-size iomem 10
clock timezone CDT -6
clock summer-time CDT recurring
no network-clock-participate slot 1
voice-card 0
no dspfarm
ip cef
voice service voip
media flow-around

8 | P a g e

allow-connections sip to sip
sip
sip-profiles 100
voice class sip-profiles 100
request INVITE sip-header SIP-Req-URI modify "; SIP/2.0" ";user=phone SIP/2.0"
request REINVITE sip-header SIP-Req-URI modify "; SIP/2.0" ";user=phone
SIP/2.0"
interface GigabitEthernet0/0
ip address x.x.x.x 255.255.255.0
duplex full
speed 100
ip http server
control-plane
dial-peer voice 100 voip
destination-pattern .T
session protocol sipv2
session target ipv4:x.x.x.x
dtmf-relay rtp-nte
codec g711ulaw
no vad
sip-ua
line con 0
line aux 0

9 | P a g e

line vty 0 4
exec-timeout 90 0
scheduler allocate 20000 1000
end
From the above coding structure we can easily state that the cube control helps huge in
controlling the entire structure under the following process that can easily determine the
network structure that has a huge prospect over the demanding structure that are quite
effectively used in the other programming standards that are quite helpful to understand each
and every prospect with great importance that are assisted for the betterment of the entire
program and for the other relevant structures that are used for coding the source that are valid
for the concept of programming in a huge prospect. This is perhaps the best windows services
that are validated with the help of different functions and classes and at the same time
influences the use of several other structures that are quite useful for the entire process. The
different functions that are used in the programming threads are quite useful for the
programmer and for the other users that can learn all the programming concepts from the
above mentioned code. The entire code is developed in Java threads and the compiler that is
used to extract the outputs is visual studio 2013. The main focus is to develop such a structure
that is quite relevant and fruitful for all the member functions and the sub classes that are
present in the above code to retain all the structure that are present in the above coding
structures. In the above codes we can also figure out that there is strong bonding among the
different patterns and directories that are used a class functions for the member functions as
the member functions helps the entire coding structure to provide the relevant details that
helps to figure out the output. The network clock and the counter debug also helps the entire
structure to go through the programming concepts so that the user can go through the codes
much effectively without any hesitation and if he faces any types of problem then he can go
through the directories and the source code and can easily figure out the problems that are
attached with the concept of programming tools that are quite useful in todays time. Hence
we can easily state form the above state that this code is the best one to describe all the
member functions and the codes that acts as supporting structures for the entire environment
that incorporates the variant codes which are quite feasible for the network structure and for
various other protocols which also acts as the member function to go through the coding
structure and available windows services.

10 | P a g e

Tester project with an XML file-700

<?xml version="1.0" encoding="UTF-8"?>
02.<!-- You may freely edit this file. See commented blocks below for -->
03.<!-- some examples of how to customize the build. -->
04.<!-- (If you delete it and reopen the project it will be recreated.) -->
05.<!-- By default, only the Clean and Build commands use this build script. -->
06.<!-- Commands such as Run, Debug, and Test only use this build script if -->
07.<!-- the Compile on Save feature is turned off for the project. -->
08.<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
09.<!-- in the project's Project Properties dialog box.-->
10.<project name="JaDaRDTester" default="default" basedir=".">
11.<description>Builds, tests, and runs the project JaDaRDTester.</description>
12.<import file="nbproject/build-impl.xml"/>
13.<!--
14.
15.There exist several targets which are by default empty and which can be
16.used for execution of your tasks. These targets are usually executed
17.before and after some main targets. They are:
18.
19.-pre-init: called before initialization of project properties
20.-post-init: called after initialization of project properties
21.-pre-compile: called before javac compilation

11 | P a g e

22.-post-compile: called after javac compilation
23.-pre-compile-single: called before javac compilation of single file
24.-post-compile-single: called after javac compilation of single file
25.-pre-compile-test: called before javac compilation of JUnit tests
26.-post-compile-test: called after javac compilation of JUnit tests
27.-pre-compile-test-single: called before javac compilation of single JUnit test
28.-post-compile-test-single: called after javac compilation of single JUunit test
29.-pre-jar: called before JAR building
30.-post-jar: called after JAR building
31.-post-clean: called after cleaning build products
32.
33.(Targets beginning with '-' are not intended to be called on their own.)
34.
35.Example of inserting an obfuscator after compilation could look like this:
36.
37.<target name="-post-compile">
38.<obfuscate>
39.<fileset dir="${build.classes.dir}"/>
40.</obfuscate>
41.</target>
42.
43.For list of available properties check the imported
44.nbproject/build-impl.xml file.

12 | P a g e

45.
46.
47.Another way to customize the build is by overriding existing main targets.
48.The targets of interest are:
49.
50.-init-macrodef-javac: defines macro for javac compilation
51.-init-macrodef-junit: defines macro for junit execution
52.-init-macrodef-debug: defines macro for class debugging
53.-init-macrodef-java: defines macro for class execution
54.-do-jar-with-manifest: JAR building (if you are using a manifest)
55.-do-jar-without-manifest: JAR building (if you are not using a manifest)
56.run: execution of project
57.-javadoc-build: Javadoc generation
58.test-report: JUnit report generation
59.
60.An example of overriding the target for project execution could look like this:
61.
62.<target name="run" depends="JaDaRDTester-impl.jar">
63.<exec dir="bin" executable="launcher.exe">
64.<arg file="${dist.jar}"/>
65.</exec>
66.</target>
67.

13 | P a g e

68.Notice that the overridden target depends on the jar target and not only on
69.the compile target as the regular run target does. Again, for a list of available
70.properties which you can use, check the target you are overriding in the
71.nbproject/build-impl.xml file.
The tester file helps the entire projects and the target system to check the entire coding
structure and the testing codes to measure effectiveness at one time. The compiler at the same
time targets the codes that are available in the run section and the other properties that uses
and over rides all the impl.xml files that are installed in the system with the help of the
launcher data system that helps the executable bin functions to be launched in to the java
program so that there is no problem in the entire program. The user also has the facility to
insert all the different compilation techniques that are used to reset a file and to build several
subclasses that would enhance the content of the java program to a huge extent. The XML
document is an important extension to the entire file system that has many other prospects
such as the major file system secure and the class building operation that also has the same
features as of the other direct extension factor that involves all the other prospect that are
readily available for the user and for the compilation techniques that are within the system
software and the target function to have a huge overview among the other section that can
possible be the best target file directory that is available worldwide for the users and for the
other sets of codes that are also designed for the same purpose (Bonaquist, 2008). Hence we
can easily state that the above XML code provides the best compilation and execution codes
that can be delivered by a system proficient generating code and by the other prospects that
helps the entire coding system to analyze the coding section and then after proceed in similar
direction that helps the entire programming prospect to move ahead effectively and join the
list of the .exe file that are quite mandatory for the entire system to grow simultaneously and
follow all the steps that are provided by the macro system in day in and day out of the coding
structure without the help of the other structure that are completely dependent on the codes
that acts as the most interactive technological system that are followed by almost every
person in this world to analyze and criticize the system codes which are available in the
coding structure of the assignment for the betterment of the system.
Ant simple sample project.
007.Instructions:

14 | P a g e

008.Put this file in an empty directory and run the 'ant' command in that directory. The build
file will create directories and make a very empty jar file in the same directory as the
build.xml.
009.
010.Create src/HW.java and put this code in it.
011.
012.public class HW
013.{
014.public static void main(String [] args)
015.{
016.System.out.println("Hello World");
017.}
018.
019.}
020.
021.in the build file below change
022.<property name="main_class_name" value="changeme"/>
023.to
024.<property name="main_class_name" value="HW"/>
025.
026.Run the ant command again, and now you can run your main class with the command
027.java -jar antsimple.jar
028.

15 | P a g e

029.It should print:
030.Hellow World
031.and exit.
032.
033.Add a junit.jar (from junit.org) into your ANT_HOME/lib directory and run 'ant test'
034.
035.Create the file test/HWTest.java and add this code.
036.import junit.framework.*;
037.public class HWTest extends TestCase {
038.public void testTrue()
039.{
040.assertTrue(true);
041.}
042.}
043.
044.-->
045.
046.<project name="antsimple" default="dist" basedir=".">
047.<description>
048.Ant Simple Sample File
049.</description>
050.<!-- set global properties for this build -->
051.<property name="ant.project.name" value="antsimple"/>

16 | P a g e

052.<property name="main_class_name" value="changeme"/>
053.<property name="jarname" value="${ant.project.name}"/>
054.<!-- set directories -->
055.<property name="src" location="src"/>
056.<property name="test" location="test"/>
057.<property name="build" location="build"/>
058.<property name="dist" location="dist"/>
059.<property name="lib" location="lib"/>
060.
061.<path id="project.classpath">
062.<pathelement location="${build}" />
063.<pathelement location="${lib}" />
064.</path>
065.
066.
067.<target name="init">
068.<!-- Create the time stamp -->
069.<tstamp/>
070.<!-- Create directories if needed -->
071.<mkdir dir="${src}"/>
072.<mkdir dir="${test}"/>
073.<mkdir dir="${build}"/>
074.<mkdir dir="${dist}"/>

17 | P a g e

075.</target>
076.
077.<target name="compile" depends="init" description="compile the source " >
078.<!-- Compile the java code from ${src} into ${build} -->
079.<javac debug="true"
080.srcdir="${src}"
081.destdir="${build}"
082.classpathref="project.classpath"/>
083.<!-- Copy files from ${src} into ${build} -->
084.<copy todir="${build}">
085.<fileset dir="${src}">
086.<exclude name="**/*.java"/>
087.</fileset>
088.</copy>
089.</target>
090.
091.<!--
092.Broken???
093.-->
094.<target name="test" depends="compiletest" description="run the tests " >
095.<junit printsummary="yes" fork="yes" haltonfailure="yes">
096.<formatter type="plain"/>
097.<batchtest fork="true">

18 | P a g e

098.<fileset dir="${test}">
099.<include name="**/*Test*.java"/>
100.</fileset>
101.</batchtest>
102.<classpath refid="${project.classpath}" />
103.</junit>
104.</target>
105.
106.<target name="compiletest" depends="compile"
107.description="compile the tests " >
108.<javac debug="true"
109.srcdir="${test}"
110.destdir="${build}"
111.classpathref="project.classpath" />
112.</target>
113.
114.<target name="dist" depends="compile" description="generate the distribution" >
115.<!-- Create the distribution directory -->
116.
117.<!-- Put everything in ${build} into the MyProject-${DSTAMP}.jar file -->
118.<jar jarfile="${dist}/${jarname}-${DSTAMP}.jar" basedir="${build}">
119.<manifest>
120.<attribute name="Main-Class"

19 | P a g e

121.value="${main_class_name}"/>
122.</manifest>
123.</jar>
124.<copy file="${dist}/${jarname}-
${DSTAMP}.jar" tofile="./${jarname}.jar"overwrite="true"/>
125.</target>
126.
127.<target name="clean"
128.description="clean up" >
129.<!-- Delete the ${build} directory-->
130.<delete dir="${build}"/>
131.</target>
132.</project>
The above xml files determines the source code that is used in the above process to determine
the core project and the other windows services that are to be availed with the help of the
cube service controller system. This is perhaps the best xml sourced code that is quite
effective for the user to understand the prospect of debug and the other programming
constraints that are equally important for the project. The user at the same time determines
the effects and directories of different source code that are specifically designed in Java and
used in the Visual Studio 2013.
Testing Phase
The test phase highlights by an empirical investigation through which the results explains the
value of the system, therefore, testing never confirms the functions of the systems perfectly
under any conditions but it can estimate that it fails under the specific conditions of the
testing process. A well- acknowledged maxim in software functioning is found earlier in the
development process which is less expensive and fixed. Testing in the beginning of the

20 | P a g e

system within the life cycle reduces risk such at the same time as the delay or cost of the
overruns due to unfinished or rejects able components. In this particular test phase, the
testing of the system signifies that the system meets all requirements which include the
security and the performance (Bragg, 2004). The in-depth security of these particular phase
shows the parts of the system which fails to satisfy the accreditation criteria. Finally, the
testing confirms the developed system which satisfies the last user who generally identifies
the needs and the requirements of the business.
Objective and Goals
The objectives and the goals of the system signifies the process of the test phase, the test
phase creates the testing process of the service by which we can identify the actual process
which is generally used in developing the service controller engine. By the objectives and
goals we can also recognize the verification of the test phase through which the successful
competition will also be seen and the process of importing and implementing the data will
also be recognized. Therefore, the goals of the test phase justifies the main aim of the test
phase, which is for providing the warranty period and the system is been build for the
purpose of testing and verifying the windows service controller.
Objectives
The test phase should verify the successful competition:
Proof by system, security and user acceptance test which helps the system to meet the
requirements, functions according to the design parameters, and then it satisfies the
business, technical, and management stakeholders.
Importing the data by the legal system.
Implementation phase approval is in progress.
The functions of the system described in the operation as well as in the user manual.
Goals
The main aim of the test phase is to provide warranty of the system, so that the system can be
building successfully and should be tested in the Development phase for the purpose of
meeting the requirements and the design parameters. When the system is been tested and
accepted then it is been moved to the Implementation phase. Then in the Implementation
phase the system is been rechecked and then it is been launched, the system takes a long time
for the process of checking because it contains many data and the software which includes an
important file for the particular system.

21 | P a g e

Deliverables and approvals
SDLC deliverables helps the state agencies in planning the successfully, and also in executing
and controlling the IT projects by lending the framework to make sure that the aspects of the
projects are perfectly and consistently planned, defined, and communicated. The SDLC
templates provide a clear structure of the needed content with the boilerplate language
agencies may customize and utilize. State agencies may also use formats other than the
templates, as long as the deliverable include all required content.
The development and the distribution of SDLC deliverables:
Enlarging natural understanding between the Development team managers and the
stakeholders.
Serve as a reminder of the specified plans as projects which generally became
increasingly complex.
Facilitate the implementation of the project management and agency IT best practices
and the results in the comprehensive record of the project performance is very useful
for various purpose.
Promote the execution of repeatable and consistent processes.
It also provides the agency senior management and other state officials which
generally insights into the risk of the project and on the ongoing performance.
The following table signifies the list of the deliverable required of all projects for the
particular phase of the work:
Deliverables Goals Develope
d By
Approved By
Test Analysis it
summarizes the
systems perceived
readiness and is
attached to the Test
Analysis Report as a
final result of the test
reviews.

Document the
perceived
production-readiness
of the system
Serve as an input to
the project Readiness
Document described
below
Team of
Developm
ent
Project Sponsor
Agency CIO

22 | P a g e


Test Problem Reports
- document problems
encountered during
testing; are also
attached to the Test
Analysis Report.

Document detailed
results of testing

Developm
ent Team
Project Sponsor
Agency CIO

Information
Technology Systems
Certification &
Accreditation -
includes completion of
a Security Risk
Assessment, Sensitive
System Security Plan,
Security Operating
Procedures, Security
Test and Evaluation,
and Certification
Statements. For SaaS
efforts, vendors may
provide alternative
documentation and
certification to provide
assurance of the same
level of security.

Assess technical and
non-technical
safeguards to
determine the extent to
which the system
meets security
requirements
Obtain formal
declaration by a
Designated Approval
Authority (DAA) that
an information system
is approved to operate
in a particular security
mode using a
prescribed set of
safeguards at an
acceptable level of risk

Development Team Project Sponsor
Agency CIO

23 | P a g e

Defect Log tracks
and summarizes in a
tabular format defects
or bugs found during
testing. Defects may
be documented via
multiple commercially
available bug tracking
tools or manually in a
spreadsheet.

Allow team members
to track reported bugs,
or defects
Clearly communicate
summary of defects
found
Record facts
regarding known bugs,
such as times reported,
individuals who
reported them, defect
statuses, and team
members responsible
for addressing the
bugs

Development Team N/A The Defect Log
does not require
approval.
Information
Technology Systems
Certification &
Accreditation -
includes completion of
a Security Risk
Assessment, Sensitive
System Security Plan,
Security Operating
Procedures, Security
Test and Evaluation,
and Certification
Statements. For SaaS
efforts, vendors may
provide alternative
documentation and

Assess technical and
non-technical
safeguards to
determine the extent to
which the system
meets security
requirements
Obtain formal
declaration by a
Designated Approval
Authority (DAA) that
an information system
is approved to operate
in a particular security
mode using a
Development Team Project Sponsor
Agency CIO

24 | P a g e

certification to provide
assurance of the same
level of security.
prescribed set of
safeguards at an
acceptable level of risk

Defect Log tracks
and summarizes in a
tabular format defects
or bugs found during
testing. Defects may
be documented via
multiple commercially
available bug tracking
tools or manually in a
spreadsheet.

Allow team members
to track reported bugs,
or defects
Clearly communicate
summary of defects
found
Record facts
regarding known bugs,
such as times reported,
individuals who
reported them, defect
statuses, and team
members responsible
for addressing the
bugs

Development Team N/A The Defect Log
does not require
approval
All the deliverables other than the identified updates should always be developed in these
particular phase. These updates should be achieved and enhanced as compulsory as arranged
in this phase. Deliverables produced during the particular phase should be reviewed in details
and should be followed by the approval path as described in the above mentioned table.
Therefore, a signature page or section is used to accompany the requiring deliverable
approval.
Recommendation
Windows operating system provides a variety of categories for audit in the occasion of
success or failure. Detailed tracking, account management, object access, policy change,

25 | P a g e

privilege use, and the system event. Auditing is disabled by default on the OS versions,
except for windows server 2003, and it should be enabled. Therefore, on the windows
operating system, post XP and server 2003, some amount of auditing is enabled by default
and should be reviewed to meet the requirements (Bragg, 2004). Therefore, on these OS
versions, additional categories and subcategories have been created for more granular
auditing control. The categories for audit in event of failure or success include account logon,
directory service access, account management, logon events, policy change, object access,
policy change, privilege use, system event, process tracking, and global object access. In the
newer versions of Windows, Audit Policy can be configured by category or subcategory. If
you define a policy by category, keep in mind that the category setting will override all
subcategory settings. Category settings can be set with group policy by configuring each
setting with the Group Policy Management Console (GPMC). Therefore, Microsoft has
established the recommended system configuration listed in this particular section for
windows server 2008 R2 base OS installations. The actual requirements are generally based
on the specific system. The Microsoft should follow the recommendation; the server should
be configured by any of the following processor families:
Intel Xeon Processor with Intel Expandable Memory 64 Technology.
Itanium-based System editions for systems with Intel Itanium Processor.
Advanced Micro Devices, Inc. Opteron
TM
series Processor.







Component Requirement
Processor Minimum: 1.4 GHz
Recommended: 2 GHz
Supports up to 256 Logical Processors
RAM per processor (socket) minimum: 512 MB
Maximum:

26 | P a g e

32 GB (Standard)
2 TB (Enterprise, Data enter, and Itanium)
Recommended: 2 GB
Monitor SVGA resolution (800x600) or higher
Optical storage DVD-ROM drive
Peripherals Keyboard
Device Microsoft Mouse or compatible pointing
Available disk space* minimum: 10 GB
Recommended: 40 GB

*Available disk space is the free disk space on the partition that will contain the system files.
Additional space is required to copy the Windows Server 2008 R2 SP1 CD contents to the
disk during installation. Computers With more than 16 GB of RAM will require more disk
space for paging and dump files.
Recommended components for ProLiant servers
You should review the following sections before installing the OS for information on the
subsystems we suggest for Windows Server 2008 R2 SP1.
Software drivers
Before installing Windows Server 2008 R2 SP1, update your systems using the HP ProLiant
Support Pack for Windows Server 2008 R2 8.70. For detail on installing the PSP, see the
Installing the ProLiant Support Pack section.
Storage Area Network components
We recommend the storage options listed in Table 4 for Windows Server 2008 R2 SP1.
For information on backup solutions, see the following websites:
HP Storage Works Enterprise Backup Solutions (EBS)
HP Backup Compatibility
As a guide to supported products and configurations, see the Windows 2008 R2 support
information on the Single Point of Connectivity Knowledge (SPOCK). SPOCK also contains
application notes, white papers, and other storage-related documents.
Therefore, some devices may have software or driver updates on the HP website or firmware
upgrades available in a Systems ROMPaq Firmware Upgrade download. The latest versions

27 | P a g e

of each software, drivers, and Systems ROMPaq are available on the HP Business Support
Centre. Before beginning the installation, always recognize the HP Business Support Centre

Conclusion
By the above mentioned project we will come to know about the Microsoft windows
operating system, the visual basic.net programming, and the services provided by the
Windows service controller. The service controller component is generally used to connect
with installed services, by using a Service controller we can start, pause, resume or stop the
services. Therefore, we can also be able to recognize the testing phase and the process of the
testing phase by which the deliverables are updated and the way by which the deliverables is
been improved. The main process of the testing phase is to emphasis the services of the
windows and to control the components. Therefore, the development team plays an important
role in the testing phase because it generally helps in recognizing the approval path of the
deliverables. In this particular project, the main aim and the goals of the system is also been
defined by the process of test phase. The test phase thereby helps the system in correcting the
data and the software of the system. Therefore, the Cube service controller controls the
windows services in a good manner which helps us in rectifying the services of the windows
and the quality of the windows. Then the most important project mentioned in this particular
project is the tester project which helps in testing the updates and the notification of the
windows services. The engine of the Cube controller service edits the various types of
programming present in the visual basic. It also helps in maintaining the software of windows
and regularly verifies the updates of the windows so that the process of the service controller
can be continued.






28 | P a g e

References
Barber, B. (2005). How to cheat at managing windows server update services. 1st ed.
Rockland, Mass.: Syngress.
Becker, R. (2012). Windows Azure programming patterns for Start-ups. 1st ed. Birmingham:
Packt Pub.
Berg, R. (1996). Resilient modulus testing of materials from Mn/ROAD, Phase 1. 1st ed.
Hanover, NH: US Army Corps of Engineers, Cold Regions Research & Engineering
Laboratory.
Bogin, G. (2010). Modeling the fuel spray and combustion process of the ignition quality
tester with KIVA-3V. 1st ed. Golden, CO: National Renewable Energy Laboratory.
Bonaquist, R. (2008). Ruggedness testing of the dynamic modulus and flow number tests with
the Simple Performance Tester. 1st ed. Washington, D.C.: Transportation Research Board.
Bragg, R. (2004). Hardening Windows systems. 1st ed. New York, N.Y.: McGraw-
Hill/Osborne.
Bragg, R. (2004). Hardening Windows systems. 1st ed. New York, N.Y.: McGraw-
Hill/Osborne.
Callahan, C. (2008). Mastering Windows SharePoint Services 3.0. 1st ed. Indianapolis, Ind.:
Wiley Pub.
Cranefield, S. and Nayak, A. (n.d.). AI 2013. 1st ed.
Dewald, B., Turley, P. and Hughes, S. (2013). SQL Server Analysis Services 2012 Cube
Development Cookbook. 1st ed. Birmingham: Packt Publishing.
Gernaey, M. and Hills, A. (2008). Programming Windows Services with Microsoft Visual
Basic 2008. 1st ed. Redmond, Wash.: Microsoft Press.
Hassell, J. (2004). Hardening Windows. 1st ed. Berkeley, CA: Apress.

29 | P a g e

Jayanty, S. (2013). Instant SQL Server Analysis Services 2012 Cube Security. 1st ed. Packt
Publishing.
Kessinger, B. and Johnson, J. (1970). Acquisition, calibration and application of a pavement
skid resistance tester. 1st ed. [Little Rock]: Arkansas State Highway Dept.
Savill, J. (2005). Windows server 2003 active directory design and implementation. 1st ed.
Birmingham, Eng.: Packt Pub.
Scribner, C. and Culver, C. (1987). National earthquake engineering experimental facility
study. 1st ed. Gaithersburg, MD: U.S. Dept. of Commerce, National Bureau of Standards.
Sheng, S. (2011). Wind turbine drivetrain condition monitoring during GRC Phase 1 and
Phase 2 testing. 1st ed. Golden, CO: National Renewable Energy Laboratory.
Tester, J. and Albright, J. (1979). Hot dry rock energy extraction field test. 1st ed. Los
Alamos, NM.: Los Alamos Scientific Lab.
Tester, J. and Modell, M. (1997). Thermodynamics and its applications. 1st ed. Upper Saddle
River, N.J.: Prentice Hall PTR.
Webb, C., Ferrari, A., Russo, M., Christie, S. and Puri, D. (2009). Expert cube development
with Microsoft SQL Server 2008 Analysis Services. 1st ed. Birmingham, UK: Packt Pub.
Wise, L. (1999). Evaluation of the voluntary national tests. 1st ed. Washington, D.C.:
National Academy Press.