The document discusses a proposed software solution from Magic Solutions for ICOMM, an Egyptian telecommunications company. Magic Solutions specializes in small to medium software solutions. The proposed solution is an IT asset tracking software that would allow ICOMM's IT department to inventory, track, and reallocate IT assets through a web-based application. The summary includes cost estimates for hardware, software licenses, and estimated development costs for a total proposed project budget of $47,900.
Describe the process of coding, testing, and converting an organizational information system and outline the deliverables and outcomes of the process.
Prepare a test plan for an information system.
Apply four installation strategies: direct, parallel, single-location, and phased installation.
List the deliverables for documenting the system and for training and supporting users.
Distinguish between system and user documentation and determine which types of documentation are necessary for a given information system.
Compare the many modes available for organizational information system training, including self-training and electronic performance support systems.
Discuss the issues of providing support for end-users.
Explain why system implementation sometimes fails.
Describe the threats to system security and remedies that can be applied.
Show how traditional implementation issues apply to electronic commerce applications.
Unit 1
Introduction to software engineering, the software as product and a process
software process models – waterfall model, incremental development, reuse
oriented software engineering, introduction to agile.
Systems approach vs engineering approach,
case studies to explain 1) the importance of information systems, 2) availability
and reliability of information systems, 3) flexibility of information systems.
Unit 2
A. Software Development process : SDLC
B. Requirements Engineering – characteristics of requirement, requirement
elicitation and analysis, validation and verification
C. Identification of attributes.
D. Feasibility Analysis : technical and economic
Unit 3
3.1Data Flow Diagrams : Symbols, describing a good system with DFD
3.2DFD : leveling of DFD, logical and physical DFD
3.3Process Specification, Decision Tables.
3.4Introduction to ER Diagrams and Data Dictionary.
Unit 4
4.1Data Input Methods : Data input, coding techniques.
4.2Designing outputs : objectives of output design, design of output reports.
4.3Software development – introduction to project and modules, coupling
and cohesion
4.4 Case studies on DFD, ERD
Unit 5.
5.1Introduction and importance of software testing
5.2Software Security concept and software maintenance
5.3Control of information system
5.4Audit of information system
Unit 6
6.1Introduction to software development and deployment environment
6.2Introduction to component based software engineering
6.3Introduction to distributed software engineering
6.4Introduction to service oriented architecture
Describe the process of coding, testing, and converting an organizational information system and outline the deliverables and outcomes of the process.
Prepare a test plan for an information system.
Apply four installation strategies: direct, parallel, single-location, and phased installation.
List the deliverables for documenting the system and for training and supporting users.
Distinguish between system and user documentation and determine which types of documentation are necessary for a given information system.
Compare the many modes available for organizational information system training, including self-training and electronic performance support systems.
Discuss the issues of providing support for end-users.
Explain why system implementation sometimes fails.
Describe the threats to system security and remedies that can be applied.
Show how traditional implementation issues apply to electronic commerce applications.
Unit 1
Introduction to software engineering, the software as product and a process
software process models – waterfall model, incremental development, reuse
oriented software engineering, introduction to agile.
Systems approach vs engineering approach,
case studies to explain 1) the importance of information systems, 2) availability
and reliability of information systems, 3) flexibility of information systems.
Unit 2
A. Software Development process : SDLC
B. Requirements Engineering – characteristics of requirement, requirement
elicitation and analysis, validation and verification
C. Identification of attributes.
D. Feasibility Analysis : technical and economic
Unit 3
3.1Data Flow Diagrams : Symbols, describing a good system with DFD
3.2DFD : leveling of DFD, logical and physical DFD
3.3Process Specification, Decision Tables.
3.4Introduction to ER Diagrams and Data Dictionary.
Unit 4
4.1Data Input Methods : Data input, coding techniques.
4.2Designing outputs : objectives of output design, design of output reports.
4.3Software development – introduction to project and modules, coupling
and cohesion
4.4 Case studies on DFD, ERD
Unit 5.
5.1Introduction and importance of software testing
5.2Software Security concept and software maintenance
5.3Control of information system
5.4Audit of information system
Unit 6
6.1Introduction to software development and deployment environment
6.2Introduction to component based software engineering
6.3Introduction to distributed software engineering
6.4Introduction to service oriented architecture
discuss about System system analysis, system design, system analyst's role, Development of System through analysis, SDLC, Case Tools of SAD, Implementation, etc.
System as a combination of resources or functional units working together to accomplish a given task. The term "working together" in system definition is very important as all the components are interrelated and interdependent and cannot exist independently.
discuss about System system analysis, system design, system analyst's role, Development of System through analysis, SDLC, Case Tools of SAD, Implementation, etc.
System as a combination of resources or functional units working together to accomplish a given task. The term "working together" in system definition is very important as all the components are interrelated and interdependent and cannot exist independently.
SysDB — The system management and inventory collection serviceSysDB Project
“System Datebase” (SysDB, https://sysdb.io/) is an Open Source daemon which aggregates system management and inventory information and stores them in a central, graph-like database. All information is (continuously) retrieved from other hardware or software systems (inventory services, monitoring services, etc. like Icinga, Puppet, collectd) and may be queried through a generic interface. SysDB focuses on meta-data like host-attributes, services and their attributes, and lists of available metrics and provides means to query data from back-end data-stores (e.g. time-series data). This way, all important information about your systems is accessible from a central location allowing for use-cases such as central dashboards, cross-link monitoring or inventory information, identify missing pieces in your system configuration, advanced monitoring configuration, and much more.
This talk provides an overview over SysDB and its features as well as sample use-cases. The project is still in an early development stage but already usable. The talk also covers future directions and further integration with existing services.
On April 11th IBM launched its converged infrastructure offering: PureSystems. We recently conducted this webinar to help customers understand the opportunity of a converged infrastructure, and the dramatic difference advanced technologies can make in the data center.
XebiaLabs, CloudBees, Puppet Labs Webinar Slides - IT Automation for the Mode...XebiaLabs
Learn how you can enhance and extend your existing infrastructure to create an automated, end-to-end IT platform supporting on-demand middleware and application environments, application release pipelines, Continuous Delivery, Private/ hybrid development platform and PaaS and more.
3. Client : ICOMM is an Egyptian company
works in Telecommunications field and considered
as a very fast growing company in the Middle East.
The company is interested in introducing new
professional solutions to the market. ICOMM uses a
web based enterprise portal for business
collaboration between different departments.
Solution Provider : Magic solutions
Is an Egyptian software house specialized in small
to medium size software solutions
*
5. SQL Server database 2
SQL Server database 2 SQL server database 1
SQL server database 1
LAN
LAN
Sharepoint portal 1
Sharepoint portal 1
Sharepoint Portal 2
Sharepoint Portal 2
Client PC
User
User
*
7. * The software will automate the process of managing all IT assets and
services inside IT department only. The user will input his request to
the system;
The system will keep track of assets, its status and owner. List of all
assets:
1. PC
2. Laptop
3. Mobile
4. Printer
5. Fax
6. Scanner
7. Network device
8. VPN device
* Customized asset categories.
* active directory integration .
* integration with the current company portal.
* Will have structured security permissions .
* Disaster recovery . *
9. <1. Project Definition> <4.Analysis> <7.Project overall evaluation>
Study of Organization analyze business functions Integrated change control
structure,mission,vision analyze information needs Cost evaluation
Identify Problems and opportunities to Evaluate current procedures
solve them Risk Monitoring and control
Develop current BPM Technical evaluation
Summerize knowladge,Estimate Project
Develop current DFD Performance tuning
scope
Analysis Report
Project scope difinition
Project Charter
<2.Develop workplan> <5.New system Proposal>
Task identification Develop new system ERD <8.Implementation>
WBS Develop new system DFD Install system
Time estimation Team meeting Sample data migration
Gantt Chart New system proposal Live test
staffing Sign off for design Mainteneance test
Cost estimation Full data migration
Determin Budget Post-implementation test
Procurment planning
Risk Analysis <6.System Design>
Work plan Design Archticture(Hardware&software)
<9.Closing>
Design Interface
Administrate closure
interface structure
Final software manual delivery
interface prototype
<3.Infotmation Gathering> End of Contract
Design programs
Observing decision making Program structure chart
Sampling Database design using ( ERD)
questionair
*
Documentation of gathered data
11. * Project description :
IT asset box is an asset tracking software designed to provide asset tracking and
inventory control for all IT assets at your organization .
Using a web based application , IT department users will be able to add remove or
reallocate assets within your corporate environment .
* Assumptions :
1. The new system will integrate with the current company portal .
2. The system is a web based application .
3. The system will run over the existing web and database server .
4. The system will be developed in house .
5. Magic solutions will perform full data migration from hard papers to software .
6. There are no formal procedures for asset tracking in Icomm
6. The system will sign –off once fully completed .
Stakeholder Position
Sponsor ICOMM IT manager
Sponsor ICOMM procurement manager
Users ICOMM IT department
Team participants Magic solutions software development team 1
*
12. Deliverables :
1. Web based application for IT asset tracking .
2. SQL2008 database .
3. The system will accept all IT assets categories
4. Permission based authentication
5. Database security and security audit .
6. Open system for future upgrade .
7. license for SQL server
8. 5 years free warranty and maintenance
9. Setup of disaster recovery solution .
Out of scope :
1. Integration with Linux systems
2. Integration with legacy systems ( before Windows XP)
3. Network or communications setup
4. Customized Graphic design
6. Bar code reader setup
Schedule : The project is estimated to take 6 months
*
17. Hardware requirements:
All items are available with the client
Item Quantity Total cost
HP ProLiant DL380 G7 Intel Xeon 2 20000 $
E5649 Processor (2.53GHz
12MB)/ 16 GB Ram
•Software requirements:
Item Quantity Total cost
SQL server 2008 standard lic. 1 11000 $
SharePoint 2010 1 4900 $
SQL user cal license 5 0$
IIS server 7.5 1. 0
•Estimated solution development cost will be calculated on the basis
•of the total number of working days where the day cost 100 $
Estimated working days = 120
Estimated software development cost = 120 *100 =12000$
•Total project budget :
Item Budget
Hardware 20000
Software 15900
Software development 12000
total 47900 $
*