A Software Engineering Perspective on SDN ProgrammabilityFelipe Alencar
Presentation of the survey published in the IEEE COMMUNICATIONS SURVEYS & TUTORIALS 2015. Software-Defined Networking (SDN) has received a great deal of attention from both academia and industry in recent years. Studies on SDN have brought a number of interesting technical discussions on network architecture design, along with scientific contributions. Researchers, network operators, and vendors are trying to establish new standards and provide guidelines for proper implementation and deployment of such novel approach. It is clear that many of these research efforts have been made in the southbound of the SDN architecture, while the northbound interface still needs improvements. By focusing in the SDN northbound, this paper surveys the body of knowledge and discusses the challenges for developing SDN software. We investigate the existing solutions and identify trends and challenges on programming for SDN environments. We also discuss future developments on techniques, specifications, and methodologies for programmable networks, with the orthogonal view from the Software Engineering discipline.
Estimating agile development in the Federal Government domain requires more than just defining Story Points and planning Sprints. These estimates must follow the guidance in OMB A-11 Part 7 and other document based management of budget and performance measures.
A Software Engineering Perspective on SDN ProgrammabilityFelipe Alencar
Presentation of the survey published in the IEEE COMMUNICATIONS SURVEYS & TUTORIALS 2015. Software-Defined Networking (SDN) has received a great deal of attention from both academia and industry in recent years. Studies on SDN have brought a number of interesting technical discussions on network architecture design, along with scientific contributions. Researchers, network operators, and vendors are trying to establish new standards and provide guidelines for proper implementation and deployment of such novel approach. It is clear that many of these research efforts have been made in the southbound of the SDN architecture, while the northbound interface still needs improvements. By focusing in the SDN northbound, this paper surveys the body of knowledge and discusses the challenges for developing SDN software. We investigate the existing solutions and identify trends and challenges on programming for SDN environments. We also discuss future developments on techniques, specifications, and methodologies for programmable networks, with the orthogonal view from the Software Engineering discipline.
Estimating agile development in the Federal Government domain requires more than just defining Story Points and planning Sprints. These estimates must follow the guidance in OMB A-11 Part 7 and other document based management of budget and performance measures.
Scaling Agile at Dell: Real-life Problems - and SolutionsTechWell
The transition from waterfall-based software development to an agile, iterative model carries with it well-known challenges and problems-entrenched cultures, skill gaps, and organizational change management. For a large, globally distributed software development organization, an entirely different set of practical challenges comes with scaling agile practices. Last year the Dell Enterprise Solutions Group applied agile practices to more than forty projects ranging from a collocated single team project to projects that consisted of fifteen Scrum teams located across the US and India. Geoff Meyer and Brian Plunkett explain how Dell mined these real-life projects for their empirical value and adapted their agile practices into a flexible planning model that addresses the project complexities of staffing, scale, interdependency, and waterfall intersection. Join Geoff and Brian to see how they tackled the tough, real-life problems scaling agile at Dell: functional-based organizational boundaries, globally distributed teams, contractor challenges, multi-team projects, and dependencies on teams that continued to develop using waterfall methods.
An Introduction to Agile Software DevelopmentSerena Software
Agile software development stresses rapid iterations, small and frequent releases, and evolving requirements facilitated by direct user involvement in the development process. Serena’s application lifecycle management tools provide a framework to visualize scope, orchestrate mundane and repetitive development tasks, and enforce process. Unlike agile-specific products offered by agile-only vendors, Serena products are methodology neutral and can be applied equally well to agile as well as more traditional serial development processes, so they can support all the development activities within an enterprise.
With the evolution and growth of technology, the IT industry is expanding at a faster rate. IT offers many jobs and positions. There are many technological changes within the industry due to advanced development. Such technological changes have led to the idea of release management as an outcome. The idea of release management emerged from the sector's shift from project-based offerings to product-based ones. The individual releases were viewed as projects instead of products before the shift. Release management delivered the role of Release Manager.
A Top 10 Key to Success for Architects, delivered by author Pete Eeles, IBM, hosted on the "Good Design is Good Business" group on developerWorks: https://www.ibm.com/developerworks/mydeveloperworks/blogs/669242b1-dd91-4d63-a08f-231314c793bb/entry/top_10_success_secrets_for_software_architects_good_design_is_good_business_series?lang=en
Why use trace cloud to manage your requirements (includes audio)Shambhavi Roy
In any large, distributed project, managing your requirements effectively determines the success of failure of the project. This slide deck identifies some common pitfalls and show solutions to better manage them
WSI32 - IBM WebSphere Performance FundamentalsHendrik van Run
IBM European WebSphere Technical Conference 2008 presentation
This lecture discusses the fundamentals of WebSphere® performance. We’ll discuss the performance lifecycle – driving performance from planning, design, development, and deployment. The session also covers the basics of the performance tuning methodology. Finally, we’ll discuss how capacity relates to the above.
Entry Skills:
• General knowledge of the WebSphere Application Server and J2EE
Exit Skills:
• Basic knowledge of the performance lifecycle
• Knowledge of performance tuning methodology
• Awareness of performance tuning resources and tools
Scaling Agile at Dell: Real-life Problems - and SolutionsTechWell
The transition from waterfall-based software development to an agile, iterative model carries with it well-known challenges and problems-entrenched cultures, skill gaps, and organizational change management. For a large, globally distributed software development organization, an entirely different set of practical challenges comes with scaling agile practices. Last year the Dell Enterprise Solutions Group applied agile practices to more than forty projects ranging from a collocated single team project to projects that consisted of fifteen Scrum teams located across the US and India. Geoff Meyer and Brian Plunkett explain how Dell mined these real-life projects for their empirical value and adapted their agile practices into a flexible planning model that addresses the project complexities of staffing, scale, interdependency, and waterfall intersection. Join Geoff and Brian to see how they tackled the tough, real-life problems scaling agile at Dell: functional-based organizational boundaries, globally distributed teams, contractor challenges, multi-team projects, and dependencies on teams that continued to develop using waterfall methods.
An Introduction to Agile Software DevelopmentSerena Software
Agile software development stresses rapid iterations, small and frequent releases, and evolving requirements facilitated by direct user involvement in the development process. Serena’s application lifecycle management tools provide a framework to visualize scope, orchestrate mundane and repetitive development tasks, and enforce process. Unlike agile-specific products offered by agile-only vendors, Serena products are methodology neutral and can be applied equally well to agile as well as more traditional serial development processes, so they can support all the development activities within an enterprise.
With the evolution and growth of technology, the IT industry is expanding at a faster rate. IT offers many jobs and positions. There are many technological changes within the industry due to advanced development. Such technological changes have led to the idea of release management as an outcome. The idea of release management emerged from the sector's shift from project-based offerings to product-based ones. The individual releases were viewed as projects instead of products before the shift. Release management delivered the role of Release Manager.
A Top 10 Key to Success for Architects, delivered by author Pete Eeles, IBM, hosted on the "Good Design is Good Business" group on developerWorks: https://www.ibm.com/developerworks/mydeveloperworks/blogs/669242b1-dd91-4d63-a08f-231314c793bb/entry/top_10_success_secrets_for_software_architects_good_design_is_good_business_series?lang=en
Why use trace cloud to manage your requirements (includes audio)Shambhavi Roy
In any large, distributed project, managing your requirements effectively determines the success of failure of the project. This slide deck identifies some common pitfalls and show solutions to better manage them
WSI32 - IBM WebSphere Performance FundamentalsHendrik van Run
IBM European WebSphere Technical Conference 2008 presentation
This lecture discusses the fundamentals of WebSphere® performance. We’ll discuss the performance lifecycle – driving performance from planning, design, development, and deployment. The session also covers the basics of the performance tuning methodology. Finally, we’ll discuss how capacity relates to the above.
Entry Skills:
• General knowledge of the WebSphere Application Server and J2EE
Exit Skills:
• Basic knowledge of the performance lifecycle
• Knowledge of performance tuning methodology
• Awareness of performance tuning resources and tools
Engine Lab Software- Hybrid Cloud Integration Specialists.
This presentation describes who we are, what we do & how we do it.
We help organisations integrate their existing legacy sysetms with cloud SaaS applications such as Dynamics CRM, Salesforce, Mobile, bespoke applications, etc...
Thanks to tools like vagrant, puppet/chef, and Platform as a Service services like Heroku, developers are extremely used to being able to spin up a development environment that is the same every time. What if we could go a step further and make sure our development environment is not only using the same software, but 100% configured and set up like production. Docker will let us do that, and so much more. We'll look at what Docker is, why you should look into using it, and all of the features that developers can take advantage of.
Thanks to tools like Vagrant, Puppet/Chef, and Platform as a Service (PaaS) services like Heroku, developers are extremely used to being able to spin up a development environment that is the same every time. What if we could go a step further and make sure our development environment is not only using the same software, but it's 100 percent configured and set up like production. Docker will let us do that, and so much more. We'll look at what Docker is, why you should look into using it, and all of the features that developers can take advantage of.
Servers are killing your productivity. Rather than building better software for your users, you end up constantly distracted by maintaining computers. Wasn't the "cloud" supposed to fix this? It sounded so promising until we realized it was just renting VMs in someone else's datacenter. We couldn't escape "servers". Until now...
In this session, developers will learn how to build microservices without servers, using modern “serverless” cloud platforms. We’ll look at common challenges (and solutions) to building applications using “serverless” stacks. Exploring emerging “serverless” design patterns will give developers the knowledge to build application architectures using these new platforms.
Presented by Jonathan Kaufman, Developer Advocate for IBM Emerging Technology currently residing in Cambridge, MA.
Computer-free Website Development Demo - WordPressDC Jan 2015Anthony D. Paul
As a follow-up to a blog post I wrote on the emergence of the computer-free designer, I gave a live demo to build, customize, and launch a WordPress site entirely from my phone, without need of a traditional computer. These were my backup slides in case the live demo wasn't possible. They contain my Terminal commands and the free apps I used.
A quick intro to docker presented at the PHP Dublin meetup, and a practical use case of using docker to run multiple PHP versions while doing software development.
Technical Webinar: By the (Play) Book: The Agile Practice at OutSystemsOutSystems
In 2001, the Agile Manifesto took the world by storm, and it changed how software is built forever. Also in 2001, OutSystems, another disruptive force in the world of traditional waterfall software development, was born.
Not coincidentally, OutSystems has been using Agile Practices all along. However, because of the sheer speed at which we’re able to respond, we’ve had to come up with a few twists in our approach. We’re even putting it into a services delivery playbook.
In our webinar, “By the (Play)Book: The Agile Practice at OutSystems,” Engagement Guild Master and Expert Nuno Fernandes will show you how OutSystems approaches Agile Development and makes sure nothing slips.
In this session you will:
- Learn roles and respective responsibilities.
- Understand project phases with a clear focus on sprint development.
- Discover how we approach the user story life cycle in particular.
- See how a really solid structure, calendar and organization help maximize productivity.
Webinar: https://www.outsystems.com/learn/courses/59/webinar-the-agile-practice-at-outsystems/
Free Online training: https://www.outsystems.com/learn/courses/
Follow us on Twitter http://www.twitter.com/OutSystemsDev
Like us on Facebook http://www.Facebook.com/OutSystemsDev
Scope Scope StatementProject TitleProject SponserObjectiveMobile technology PlanVodafone IncSmart Phone Mobile Technology with safety devices, data entry operations,reliable and information sharing system.Executive Summary The business goals and objectives for this project will focus on implementing mobile technology that:
1. Create safety for officer, fire safety and citizens.
2. Help in coordinating in information sharing to both internal and external to the participant institutions.
3. Helps to create effectiveness amongst staff skill sets.
4. Facilitate electronic capturing of data at its source.
5. Eliminate irrelevant data entry jobs in the organization.
6. Ensure high data reliability.
7. Reduce unauthorise access and electronic crime.
8. Provide user friendly and fexible technology base for the future years.
Project Scope Statement The Project will introduce new mobile technology; including the following:
1. 3G/4G Networking
2.GPS device
3.Car to car messaging
4.Internet access
5.Mobile Gaming
6.One touch File sharing.
7.Various Other Interfaces like CAD,RMS,TlETS,AFR etcThe project does not include the following:
Devices in supervisor vehicles
Desktop hardware upgrade or replacement
Printers
MilestonesROM Budget The Overall funding requirement for this project will be $5000- $7000Milestone 1 -Secure agreement with vendors ( L3 & Tiburon)- 1 WeekMilestone 2- Order and Install equipment.- 2-4 WeeksMilestone 3- Install and test software.- 2-3 WeeksMilestone 4 - Conduct Hardware and software testing- 2 weeksMilestone 5 -Conduct training and implement ARS/AFR- 3-4 weeksInitial OrganizationThe engineering team will consist of Eight groups: Steering committee,Project sponsor, Project Manager,Design, Software, Hardware, Assembly, and TestingProduct DescriptionProject Roles and ResponsibilitiesRoleResponsibilitiesParticipant(s)Project Sponsor§ To approve the project or notMohammed§ Review the project thoroughly§ Suggest improvisations in the projectSteering Committee§ Approves the funding and resourcesNasser and team§ Allocate strategies, and suggest changes§ If any conflicts and issues crops up, help in resolving it§ Provide assistance to the Project Manager§ Review project deliverablesProject Manager§ Manages project according to the project planTo be identified by Steering committee§ Work in accordance with the Steering Committee§ Provides supervision to consultants and vendors§ Keeps a check on progress of project§ Guide the team members to achieve the goal and objectives§ Motivates and encourages team members§ Provide training to the team members§ Manages the project budgetProject Participants§ Visualize needs of customer and businessTo be identified by Steering Committee § Participates in market survey to understand marketing strategies§ Participate in seminars and meeting conducted by project manager.§ Communicate about the status and progress of the project and report to higher authority.§ Review the ma.
Indonesia Truck Entry Project Proposal (1) [Autosaved].pptxbidyut13
Digitize the logistic operations in Indonesia with the use of Advance Analytics
Reduce the wait time of freight at different touch points (entry gate, exit gate and docks) in a warehouse, in turn will help reduce load/unload throughput time
Enhanced visibility of logistic operations for management to identify opportunities for improvement and take actions accordingly
Software Development: Fixed Price Model FeaturesVladimir Tursin
This presentation is an insight into Fixed Price model of outsourced software development. Here is a description of Fixed Price model, its budget components, project development process and other details. Prepared by Belitsoft.
Ray Business Technologies Process Methodologyray biztech
Ray Business Technologies (“RAYBIZTECH”)
IT process methodology is modeled after Open
Unified Process (Open UP
), an iterative and requirements
-
driven agile methodology for project
deliveries. Key checks and balances are done at each milestone to ensure that requirements
are properly implemented with high quality. The model comprises of iterations delivering
increments in functionality to deliver the solution.
How develop a specification for a new software and/or App.
We remember how to collaborate with stakeholders, define types of requirements and examine a structure of the IEEE SWEBOK SRS template.
How develop a specification for a new software and/or App.
We remember how to collaborate with stakeholders, define types of requirements and examine a structure of the IEEE SWEBOK SRS template.
VoIP Implementation WBSTask NameDurationStart DateEnd DatePredeces.docxjessiehampson
VoIP Implementation WBSTask NameDurationStart DateEnd DatePredecessors% CompleteStatusAssigned ToCommentsStartFinishCritical1. Intiation14d10/02/1910/15/1999%CompleteJevin 1.1 Recommendation & evaluation3d10/02/1910/04/19100%CompletedJenny 1.2 Project chart Deveelopment2d10/05/1910/06/19100%CompletedJenny 1.3 Outline of deliverable2d10/07/1910/08/19100%CompletedMark 1.4 Stakeholders analysis3d10/09/1910/11/194100%CompletedJoe 1.5 Charter signed by Authority4d10/12/1910/15/1995%In ProgressJoe2. Planning22d10/16/1911/07/19 2.1 Make a scope management2d10/16/1910/17/190%Not StartedJudy 2.2 Design the project team4d10/18/1910/21/090%Not StartedMolly 2.3 Intial meeting to boost the project3d10/22/1910/24/190%Not StartedMolly 2.4 Development of project plan2d10/25/1910/26/19130%Not StartedJudy 2.4.1 Create the schedules2d10/27/1910/28/190%Not StartedAlex 2.4.2 Analysis the critical path3d10/29/1911/01/190%Not StartedAlex 2.5 Submission of Project plan4d11/02/1911/05/190%Not StartedTim 2.6 Approval for project Plan2d11/06/1911/07/19120%Not StartedTiana3. Designing20d11/08/1911/27/19 3.1 Meeting to boost the team2d11/08/1911/09/190%Not StartedMandy 3.2 Verify the user requirements3d11/10/1911/12/190%Not StartedMandy 3.3 Designing of system4d11/13/0911/16/190%Not StartedKathy 3.4 procurement of software and hardware3d11/17/1911/19/190%Not StartedKathy 3.5 Installation of development system2d11/20/1911/21/190%Not StartedTim 3.6 Initiate testing3d11/22/1911/24/190%Not StartedHarry 3.7 Installation of live system2d11/25/1911/26/19200%Not StartedHarry 3.8 Training of users1d11/27/1911/27/190%Not StartedTiana4. Control20d11/28/1912/18/19 4.1 Management of Project4d11/28/1912/01/190%Not StartedMolly 4.2 Meetings to track the status of the meeting4d12/02/1912/05/190%Not StartedMolly 4.3 Risk management8d12/06/1912/13/190%Not StartedManoj 4.4 Updation of project management plan5d12/14/1912/18/190%Not StartedMandy5. Closing11d12/19/1912/29/19 5.1 Audit procurement4d12/19/1912/22/190%Not StartedAlisha 5.2 Updating and revision of documents2d12/23/1912/24/19300%Not StartedPrem 5.3 Update records and files2d12/25/1912/26/190%Not StartedHari 5.4 Receive the acceptance formally1d12/27/1912/27/190%Not StartedJames 5.5. Archieve Documents and files2d12/28/1912/29/190%Not StartedJames
Comments
Running Head: PROJECT PLAN-BUSINESS REQUIRMENT DOCUMENT 1
PROJECT PLAN-BUSINESS REQUIRMENT DOCUMENT 21
Project Plan-Business Requirement Document
CIS 599 Graduate Info Systems Capstone
Abstract
After finishing project plan inception with introduction Docume ...
2. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
HCS - Data Migration to
CarePortal
Project
Overview
Indicate brief description of Dev Project
SDS Framework outline the activities performed at each stage of a software development project:
Phase 1 - Project Identification
Phase 2 - Requirement Analysis
Phase 3 - Establish PMO
Phase 4 - Project Scoping
Phase 5 - Design and Development
Phase 6 - Testing/Modification/Revision
Phase 7 - Pilot
Phase 8 - Deployment
Phase 9 - Post Implementation
Phase 10 - Project Closure
3. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
HCS - Data Migration to
CarePortal
Project
Overview
Indicate brief description of Dev Project
Phase 1 - Project Identification
Brief description/overview of project coming from project sponsor… this should be filled
out by the Project Sponsor/Representative
4. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
HCS - Data Migration to
CarePortal
Project
Overview
Indicate brief description of Dev Project
Phase 2 – Requirement Analysis
Project Sponsor to define needed information, function, behavior, performance and
processes.
5. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
HCS - Data Migration to
CarePortal
Project
Overview
Indicate brief description of Dev Project
Phase 3 – Establish PMO
SDS and Project Sponsor to define and establish Project Management Team,
communication standards, escalation process and reporting structure. A separate
deck will be provided to the project sponsor thru SDS assigned Project Manager
6. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
HCS - Data Migration to
CarePortal
Project
Overview
Indicate brief description of Dev Project
Phase 4 – Project Scoping
SDS Project Manager to work hand in hand Project Sponsor to provide a detailed
project scope.
Project Scoping is further divided in two Phases:
1. Basic Scoping – an initial Project Scoping document which is included in this
document will be provided by SDS to the Project Sponsor
2. Detailed Scoping – will be conducted by SDS Project Manager after reviewing Basic
Scoping Document
7. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
HCS - Data Migration to
CarePortal
Project
Overview
Indicate brief description of Dev Project
Phase 5 – Design and Development
SDS Project Manager will work with SDS Dev Team to begin with the design and
development of the Project
Phase 6 – Testing/Modification/Revision
Initial version release will be provided and facilitated by SDS Project Manager which
will work together with the Project Sponsor’s Team to perform and document testing,
identify modification/revision needed.
Phase 7 – Pilot
Depending on the size of the project as well as Project Sponsor’s and business
requirement a Pilot or soft launch will be scheduled and perform to ensure proper
transition
8. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
HCS - Data Migration to
CarePortal
Project
Overview
Indicate brief description of Dev Project
Phase 8 – Deployment
Once Testing and Pilot has been conducted deployment to production will be
performed. In depth deployment details will be outlined and included on the project
plan.
Phase 9 – Post Implementation
After successful application deployment a post implementation review will be
conducted by SDS Project Manager together with Project Sponsors
Phase 10 – Project Closure
SDS Project Manager will provide all project documentation for final review with the
Project Sponsor. Project Document will be achieved by SDS PMO for future reference.
9. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
Project
Overview
Indicate brief description of Dev Project
Phase 4A – Basic Project Scoping
Company Name
Address
Project Name
Project Sponsor
Department
Contact Info
Email
Phone Numbers
Fax Number
Project Duration (in days/hours)
10. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
Project
Overview
Indicate brief description of Dev Project
Phase 4A – Basic Project Scoping
Business Requirements: (pls enumerate below)
11. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
Project
Overview
Indicate brief description of Dev Project
Phase 4A – Basic Project Scoping
Application Model: (please select which ever is/are applicable for the project)
Hosted (Cloud base)
On Premise (In house Server)
Centralize Database
Localize Database
Single User
Multiple User
Single Location
Multi-Location
Stand alone Application
Integrated to other existing Application
12. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
Project
Overview
Indicate brief description of Dev Project
Phase 4A – Basic Project Scoping
Process Model: pls define the existing process model , where a pictorial top-down
representation of the major business processes that interact with the system is
diagrammed and decomposed into manageable functions and sub-functions
until no further breakdown is feasible; if there will be a process improvement
that needs to be incorporated with the system/application development kindly
provide the process details as well; some expected output for this are:
• Work Flow Diagram
• Process Flow Model
• User Event Diagram
• Decision Trees
13. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
Project
Overview
Indicate brief description of Dev Project
Phase 4A – Basic Project Scoping
Logical Data Model : pls define data that supports the processes and business
rules, how it is logically modelled; identify entities, their relationships and
dependencies to other entities as well as attributes with their business
definitions; some expected output for this are:
• Entity Relationship Diagram
• Logical Data Dependency Diagram
14. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
Project
Overview
Indicate brief description of Dev Project
Phase 4A – Basic Project Scoping
Functional Specification : please define interfaces, processes and data are
merged to describe systematically how the end-user will use the application,
and how data will be retrieved, processed and stored; please list down system
features of the system that will specifically satisfy a user need, or with which
the user will directly interact; some expected output for this are:
• Process Association and Grouping
• Logical Organization
• Work Flow Clustering
• Expressing Logic: Pseudo Code, Structured English, Object Oriented
Logic
• User wish list
15. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
Project
Overview
Indicate brief description of Dev Project
Phase 4A – Basic Project Scoping
Technical Specification : please define or identify the technical constraints or
conditions under which the system must perform such as but not limited to:
• Accessibility
• Encryption
• Company Technology Guidelines/Requirements
• System Operations and Maintenance
• Data Protection and Integrity
16. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
Project
Overview
Indicate brief description of Dev Project
Phase 4A – Basic Project Scoping
Operational Specification : please define or identify the requirements that define
those “behind the scenes” functions that are needed to keep the system
operational over time such as but not limited to:
• System Performance and responsiveness
• Data Archival
• Audit and Controls
• System Administration
• Business Continuity
17. Any use, copying, distribution in any means without the written
consent of SDSolutions I.T. Outsourcing, Inc. is strictly prohibited
Project Partners Details
Project Manager Mario Umali
Project Phase NA
Document Tyep Dev ASM Kit
Project
Overview
Indicate brief description of Dev Project
Phase 4A – Basic Project Scoping
Transition Requirements : please define or identify the requirements that define
those aspect that must be addressed in order for the system to be successfully
implemented in the production environment and to avoid work flow disruption
during transition, such as but not limited to:
• Data Conversion
• Release Validation
• System/Technical/User documentation
• Training
• Mechanics or deployment standard procedure
• Logistics