3. Main Topics
• Solution4Tech Mission
• Cell Phone Standards and Protocols
• Requirements for Software Life Cycle
• Capability Maturity Model Integration (CMMI) & Requirements
Management Process Area (REQM)
• RequirementTestTools
• Requirements Management and Metrics
10/30/16 3VetMobileLink
5. 0 1 2 3 4 5 6
0 G
1G
2G
3G
4G
5G
History of Mobile Communications
Breakthrough
6. Standardizations by ANSI, 3rd generation
partnership project (3GPP), and Others
3GPP Organization Country
EuropeanTelecommunications Standards
Institute
ETSI Europe
TelecommunicationTechnology Committee TTC Japan
Association of Radio Industries and Businesses ARIB Japan
Alliance forTelecommunications Industry
Solutions
ATIS USA
China Communications Standards Association CCSA China
TelecommunicationsTechnology Association TTA Korea
10/30/16 6VetMobileLink
Notable Standards
• 2G
• TDMA
• D-AMPS IS-136 by ANSI
• CDMA 2000 IS-95 by ANSI
• GSM by MoU
• 3G
• GSM Evolution (EDGE)
• Evolution Data Optimized
(EVDO)
• Wide Band CDMA
(WCDMA)
• 4G
• LTE
8. CMMI & REQM
VetMobileLink 10/30/16 8
CMMI
• Purpose
• 22 Process Areas (PA)
• Related Process Areas
• Specific Goals (SG) and
Practices (SP)
• Generic Goals and
Practices
• Levels
REQM
• Purpose
• Introductory Notes
• Related Process Areas
• SG1
• SP1-5
9. REQUIREMENTS MANAGEMENT TOOLS
VetMobileLink 10/30/16 9
Test Plan
• Step 1 – Review the Requirements
• Step 2 –Write aTest Plan
• Step 3 – Identify theTest Suite
• Step 4 – Name theTest Cases
• Step 5 –WriteTest Case Descriptions and Objectives
• Step 6 - Create theTest Cases
• Step 7 - Review theTest Cases
13. VetMobileLink 10/30/16 13
References
Software development life cycle (SDLC). (2003). In B. Pfaffenberger, Webster's NewWorld&Trade;Computer Dictionary.
Boston, MA: Houghton Mifflin Harcourt. Retrieved from
http://search.credoreference.com/content/entry/webstercom/software_development_life_cycle_sdlc/0
Systems design and life cycle. (2013). In BCS Glossary of computing and ICT. Swindon, United Kingdom: BCS,The
Chartered Institute for IT. Retrieved from
http://search.credoreference.com/content/entry/bcscompict/systems_design_and_life_cycle/0
Remy, J.-G, & Letamendia,C. (2014). LTE standards [Proquest]. Retrieved from
http://proquestcombo.safaribooksonline.com.proxy.cecybrary.com/book/electrical-engineering/communications-
engineering/9781119043607
Waldock, B. (2015). Being agile in business: Discover faster, smarter, leaner ways to succeed at work [Proquest]. Retrieved
from http://proquestcombo.safaribooksonline.com.proxy.cecybrary.com/book/quality-management/9781292083735
Bourque, P., Fairley, R. E., & IEEE Computer Society. (2014). Guide to the software engineering body of knowledge [PDF]
(3rd ed.). Retrieved from https://www.computer.org/web/swebok/v3
Carnegie Mellon University. (2010). CMMI for development [PDF] (1.3rd ed.). Retrieved from
http://resources.sei.cmu.edu/library/asset-view.cfm?assetid=9661
Lewis,W. E., Dobbs, D., &Veerapillai,G. (2009). Software testing and continuous quality improvement [Books24x7].
Retrieved from
http://library.books24x7.com.proxy.cecybrary.com/assetviewer.aspx?bookid=26474&chunkid=926364570&rowid=125¬
eMenuToggle=0&hitSectionMenuToggle=0&leftMenuState=1
Editor's Notes
Cell Phone Standards and Protocols
This will provide a brief overview of current standards and protocols
History of Cell Phone evolution
So what is a Software Development Life Cycle (SDLC)
It’s a very straight forward acronym which correlates to Software Solutions from beginning to end
We will be taking a look at the phases and where requirements fall in SDLC’s
CMMI is the mecca of process improvement and standards and practices
Who Made CMMI and why is it important
SEI
We will talk about process areas
We will talk about Maturity Levels
Requirements Management process area REQM
We will talk about this Process Area
Define the overall idea of REQM
Talk about SP’s and SG’s
Talk about GP’s and GG’s
Relationship of process areas
Validation
REQM Tools
This sections is in regards to requirements management through tools of testing
REQM and Metrics
Once we have a solid foundation of REQM and have used the tools how do we know we are on the right track.
We will discuss Metrics which can measure criteria to ensure incessant improvement
Ok So why choose Solution4Tech to implement a software system solution?
Solution4Tech is a Software System Solution company which delivers excellence through an unmatched ability to transduce customer and business requirements into solutions which are upheld to the integrity of the established or intended culture for which the service is needed.
Solution4Tech uses standard, practices, and protocols for all process areas of Information Technology (IT) solutions. You can rest assured that any IT solution that Solution4Tech has involvement in, is comprehensively delivered, meeting the needs of the customer’s, user’s, and businesses.
Thorough documentation and a disciplined approach from commencement to completion. Solution4Tech clearly articulates the comprehensive process with follow-through, approval through authorization, and translucent traceability
Our Mission
We are in business to make you happy, solve your problems, and optimize and integrate. We are not happy unless the intended user and/or service provided makes all that interact with the solution exultant.
We are in business to provide a service and achieve an undeniably inclusive approval from all.
3 I’s
We are committed to perpetual enhancement and method improvement indefinitely. Persistently exceling to yield limitless potential and ever-present possibilities
3 A’s
By asking better questions, we get better answers. It starts with identifying the area for development, recognizing opportunities and application through action.
3 C’s
We understand that an integrated software solution is supposed to work entirely as one comprehensive solution combining multiple facets to one central source
OG
The original network first stated its claim in the US in 1940, but it wasn’t until the 1960’s – 1980’s that a lot of mobile communication systems were developed for calling and paging ().
1G – 1970’s
During the 70’s computer drive frequency tuning enable precise tuning
Standardization began to take place
The first advance mobile phone system (AMPS) and the predominant features we standardized by the American National Standard Institute (ANSI) ()
2G - 1980’s
Vocoders, the key to switch from analog FM to full digital transmission, were developed and mobile communications were digitalized ().
3G – 1990 – 2000’s
The need for increased data broadcast speeds expands but Transmission Control Protocol-Internet Protocol (TCP-IP) was very slow ().
The industry getting progressively competitive High Speed Packet Access (HSPA) was deployed servicing data users optimally ().
4G - Current
ATT pursues data and launches the LTE project which would be completely based on IP implementing a more suitable architecture and became the standard of mobile communication ().
5G – The future
Orthogonal frequency-division multiplexing (OFDM) is recognized as the best means for transferring data and mass adopted by Wi-Fi (IEEE 802.11n), power line communications (PLC), and television broadcasters ().
Smartphones are able to communicate through Wi-Fi
LTE Advanced is accepted as IMT-Advanced relevant Solution in late 2010 ().
2g
CDMA – Code division multiple access (Remy & Letamendia, 2014)
at first CDMA is rejected because of the inability to produce fast enough chips and time division multiple access (TDMA) was chosen (Remy & Letamendia, 2014)
IS-136 used advanced mobile phone system AMPS channels in TDMA mode increasing network data bandwidth exponentially (Remy & Letamendia, 2014)
IS-95 was adopted first by South Korea and it was not until the 1990’s that the processor chips were manufactured enabling sufficient power (Remy & Letamendia, 2014)
3G
EDGE standardized 240 kbps (Remy & Letamendia, 2014)
EVDO used two networks for telephony and data which solved freedom of movement issues (Remy & Letamendia, 2014)
Although premature WCDMA was standardized and it took a decade to manage the power consumption(Remy & Letamendia, 2014)
It was then later renamed HSPA (Remy & Letamendia, 2014)
4G
Release 8 from 3GPP in 2008 officially standardized LTE and it was the answer to the ITU’s request to provide the future mobile system which ended on the name IMT Advanced (Remy & Letamendia, 2014)
5G
Currently isn’t very popular and adopted by select few with LTE IMT Advanced (Remy & Letamendia, 2014)
The SDLC has two typical approaches which traditional and agile.
Traditional Methodology
The depicted approach above is a traditional type of SDLC where each phase must be fully completed prior to moving on to the next phase and typically phases are not revisited unless major issues have arisen. Typically a traditional approach such as the waterfall method have two outcomes which are success or failure
Agile Methodology
An agile SDLC is based around continuous learning which incorporates learning and reflecting after each iteration or action but significantly minimizes failure.
Essentially lesser additive advances headed for success (Software design and life cycle, 2013)
A common practice prior to SDLC development is a feasibility study which includes estimates of cost, effort, effectiveness, reliability, and expected benefit of new solution (Software design and life cycle, 2013).
CMMI is a knowledge based guide which focuses on process enhancement which helps to tackle scalability developed by the Software Engineering Institute at Carnegie Mellon University (CMMI, 2010).
The 22 process areas are the main focal point of CMMI and range from core organizational processes to management and quality assurance.
Each PA has (Carnegie Mellon University, 2010)
purpose statement
introductory notes
related PA’s
Specific Goals and practices
Ex. Work products and subpractices
Generic Goals and practices
Subpractices and generic elaborations
Levels (Carnegie Mellon University, 2010)
Maturity Levels
Concerned with simultaneous PA improvement
The five levels must be done successively corresponding to the correct PA’s
Capability Levels
Concerned with a single PA improvement
PA’s can be skipped and selected at random
REQM is at the lowest level which is a maturity level 2 PA. An organization starts out at level 1 and once completion of all goals the organization will improve to a level 2 standing (Carnegie Mellon University, 2010).
Purpose (Carnegie Mellon University, 2010).
Just as the name in insinuates, REQM is used to manage requirements to help with characteristic arrangements of the project plan, work products, and requirements
Introductory Notes (Carnegie Mellon University, 2010).
Helps to manage
Technical requirements
Nontechnical requirements
Concurrent PA implementation of Requirements Development, Requirement Management, and Technical Solution (TS) optimize performance
Documents requirements
Bidirectional Traceability
Related Process Areas (Carnegie Mellon University, 2010).
Requirements Development
TS
Configuration Management
Project Monitoring and Control
Project Planning
Risk Management
SG1 Manage Requirements (Carnegie Mellon University, 2010).
Understand
Example of evaluation and acceptance criteria for understanding requirements
Traceability
Verifiable/testable
Achievable
Obtain Commitment
Manage Changes
Change request
Maintain bidirectional traceability
Work products
Traceability matrix
Tracking system
Ensure proper alignment with work project
Work products
Document inconsistencies
Corrective action
This Seven Step Test Plan Contains an enormous number of tools for requirements management (Lewis, Dobbs, & Veerapillai, 2009)
Step 1
Prepare reviewers with checklist of common requirement errors for focal guidance
Inviting the correct experts for the review
Provide heightened importance on critical issues that could be extremely far-reaching further down the life cycle
Keep a question list to ask the right questions and avoid common forgetfulness
Refer team members to the updated requirements document
Step 2
Test plan focal points
Ranked value of goals for release
Declaring activities for the test to accomplish expected goals
Assessing the perceived successfulness of the assisting goals
Strategizing the tasks to conduct activities checklist
Step 3
Design test suites
Identify the input of test cases like types of operations
Step 4
Name test cases and utilize TBD were applicable
Step 5
Keep test cases simple with clear description and objectives
Step 6
Conduct design and implementation with focus on
Heightened priority use cases and features
Components of the software solution currently available to test
Features are prerequisites to other features
Features needed for presentation or alike
Requirement which are left unclear
Step 7
Evaluate test suits for wide-reaching ability by readability and clear table of contents and that all individual test cases actual correlate with all input values required
SWEBOK (Bourque, Fairley, & IEEE Computer Society, 2014)
Follow the standards and practices to the breakdown of Software Requirement topics such as
Fundamentals
Process
Elicitation
Analysis
Specification
Validation
Consideration
And tools
Metric examples
Change management
requirement tracing
Software development life cycle (SDLC). (2003). In B. Pfaffenberger, Webster's New World&Trade; Computer Dictionary. Boston, MA: Houghton Mifflin Harcourt. Retrieved from http://search.credoreference.com/content/entry/webstercom/software_development_life_cycle_sdlc/0
Systems design and life cycle. (2013). In BCS Glossary of computing and ICT. Swindon, United Kingdom: BCS, The Chartered Institute for IT. Retrieved from http://search.credoreference.com/content/entry/bcscompict/systems_design_and_life_cycle/0
Remy, J.-G, & Letamendia, C. (2014). LTE standards [Proquest]. Retrieved from http://proquestcombo.safaribooksonline.com.proxy.cecybrary.com/book/electrical-engineering/communications-engineering/9781119043607
Waldock, B. (2015). Being agile in business: Discover faster, smarter, leaner ways to succeed at work [Proquest]. Retrieved from http://proquestcombo.safaribooksonline.com.proxy.cecybrary.com/book/quality-management/9781292083735
Bourque, P., Fairley, R. E., & IEEE Computer Society. (2014). Guide to the software engineering body of knowledge [PDF] (3rd ed.). Retrieved from https://www.computer.org/web/swebok/v3
Carnegie Mellon University. (2010). CMMI for development [PDF] (1.3rd ed.). Retrieved from http://resources.sei.cmu.edu/library/asset-view.cfm?assetid=9661
Lewis, W. E., Dobbs, D., & Veerapillai, G. (2009). Software testing and continuous quality improvement [Books24x7]. Retrieved from http://library.books24x7.com.proxy.cecybrary.com/assetviewer.aspx?bookid=26474&chunkid=926364570&rowid=125¬eMenuToggle=0&hitSectionMenuToggle=0&leftMenuState=1
