We found 94 results that contain "software"
Posted on: #iteachmsu
Playlist: Importance of Software Testing ?
It’s common for many startups to skip testing. They might say that their budget is the reason why they overlook such an important step. They think it would lead to no major consequences. But to make a strong and positive first impression, it needs to be top-notch. And for that, testing the product for bugs is a must.
To really understand why software testing is important, we need to correlate it with real world examples, which has caused serious issues in the past, a few examples include:
In October 2014, Flipkart an e-commerce in India company had an offer called the “Big Billion Sale.” When it was launched it had a lot of traffic and as a result, its website couldn’t handle the enormous load of traffic leading to the website downtime, cancellation of orders etc. The reputation of the organization was badly impacted by this issue.
In 2015, the Royal Bank of Scotland, due to a bug, couldn’t process about 600,000 payments. Because of this, they were fined 66 million pounds
Yahoo in September 2016, had a major data breach where 500 million users’ credentials got compromised.
Recently, Okta, an American authentication firm, had a digital breach due to a software bug that may have affected their user’s details. This has also affected the reputation of Okta.
Similarly, established organizations need to maintain their client base and their impression. So they have to ensure the delivery of flawless products to the end-user. Let’s take a look at some points and see why software testing is vital to good software development.
To really understand why software testing is important, we need to correlate it with real world examples, which has caused serious issues in the past, a few examples include:
In October 2014, Flipkart an e-commerce in India company had an offer called the “Big Billion Sale.” When it was launched it had a lot of traffic and as a result, its website couldn’t handle the enormous load of traffic leading to the website downtime, cancellation of orders etc. The reputation of the organization was badly impacted by this issue.
In 2015, the Royal Bank of Scotland, due to a bug, couldn’t process about 600,000 payments. Because of this, they were fined 66 million pounds
Yahoo in September 2016, had a major data breach where 500 million users’ credentials got compromised.
Recently, Okta, an American authentication firm, had a digital breach due to a software bug that may have affected their user’s details. This has also affected the reputation of Okta.
Similarly, established organizations need to maintain their client base and their impression. So they have to ensure the delivery of flawless products to the end-user. Let’s take a look at some points and see why software testing is vital to good software development.
Posted on: #iteachmsu
Software engineering
Software engineering is an engineering branch associated with development of software product using well-defined scientific principles, methods and procedures. The outcome of software engineering is an efficient and reliable software product.
Software project management has wider scope than software engineering process as it involves communication, pre and post delivery support etc.
This tutorial should provide you basic understanding of software product, software design and development process, software project management and design complexities etc. At the end of the tutorial you should be equipped with well understanding of software engineering concepts.
Software project management has wider scope than software engineering process as it involves communication, pre and post delivery support etc.
This tutorial should provide you basic understanding of software product, software design and development process, software project management and design complexities etc. At the end of the tutorial you should be equipped with well understanding of software engineering concepts.
Posted on: #iteachmsu
Importance of Software Testing
It’s common for many startups to skip testing. They might say that their budget is the reason why they overlook such an important step. They think it would lead to no major consequences. But to make a strong and positive first impression, it needs to be top-notch. And for that, testing the product for bugs is a must.
Posted on: #iteachmsu

Software-as-a-Service (SaaS)
Software-as-a-Service (SaaS) :
Software-as-a-Service (SaaS) is a software licensing model in which access to the software is provided on a subscription basis, with the software being located on external servers rather than on servers located in-house. Software-as-a-Service is typically accessed through a web browser, with users logging into the system using a username and password. Instead of each user having to install the software on their computer, the user is able to access the program via the internet.
SaaS has many business applications, including file sharing, email, calendars, customer retention management, and human resources.
Software-as-a-Service (SaaS) is a software licensing model in which access to the software is provided on a subscription basis, with the software being located on external servers rather than on servers located in-house. Software-as-a-Service is typically accessed through a web browser, with users logging into the system using a username and password. Instead of each user having to install the software on their computer, the user is able to access the program via the internet.
SaaS has many business applications, including file sharing, email, calendars, customer retention management, and human resources.
Posted on: Software testing
Playlist : What Do You Mean By Software Testing?
Software testing is the process of finding errors in the developed product. It also checks whether the real outcomes can match expected results, as well as aids in the identification of defects, missing requirements, or gaps.
Testing is the penultimate step before the launch of the product to the market. It includes examination, analysis, observation, and evaluation of different aspects of a product.
Professional software testers use a combination of manual testing with automated tools. After conducting tests, the testers report the results to the development team. The end goal is to deliver a quality product to the customer, which is why software testing is so important.
Testing is the penultimate step before the launch of the product to the market. It includes examination, analysis, observation, and evaluation of different aspects of a product.
Professional software testers use a combination of manual testing with automated tools. After conducting tests, the testers report the results to the development team. The end goal is to deliver a quality product to the customer, which is why software testing is so important.
NAVIGATING CONTEXT
Posted on: Software testing
Importance of Software Testing
It’s common for many startups to skip testing. They might say that their budget is the reason why they overlook such an important step. They think it would lead to no major consequences. But to make a strong and positive first impression, it needs to be top-notch. And for that, testing the product for bugs is a must.
To really understand why software testing is important, we need to correlate it with real world examples, which has caused serious issues in the past, a few examples include:
In October 2014, Flipkart an e-commerce in India company had an offer called the “Big Billion Sale.” When it was launched it had a lot of traffic and as a result, its website couldn’t handle the enormous load of traffic leading to the website downtime, cancellation of orders etc. The reputation of the organization was badly impacted by this issue.
In 2015, the Royal Bank of Scotland, due to a bug, couldn’t process about 600,000 payments. Because of this, they were fined 66 million pounds
Yahoo in September 2016, had a major data breach where 500 million users’ credentials got compromised.
To really understand why software testing is important, we need to correlate it with real world examples, which has caused serious issues in the past, a few examples include:
In October 2014, Flipkart an e-commerce in India company had an offer called the “Big Billion Sale.” When it was launched it had a lot of traffic and as a result, its website couldn’t handle the enormous load of traffic leading to the website downtime, cancellation of orders etc. The reputation of the organization was badly impacted by this issue.
In 2015, the Royal Bank of Scotland, due to a bug, couldn’t process about 600,000 payments. Because of this, they were fined 66 million pounds
Yahoo in September 2016, had a major data breach where 500 million users’ credentials got compromised.
Posted on: #iteachmsu
By super admin: What is the Agile Manifesto Software Development? -- edited
What is the Agile Manifesto Software Development?
PEDAGOGICAL DESIGN
Posted on: #iteachmsu

Agile
We are uncovering better ways of developing software by doing it and helping others do it. Through this work, we have come to value −
Individuals and interactions over Processes and tools
Working software over Comprehensive documentation
Customer collaboration over Contract negotiation
Responding to change over Following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Individuals and interactions over Processes and tools
Working software over Comprehensive documentation
Customer collaboration over Contract negotiation
Responding to change over Following a plan
That is, while there is value in the items on the right, we value the items on the left more.
ASSESSING LEARNING
Posted on: #iteachmsu

Article For Software development life cycle
What is SDLC?
SDLC is a process followed for a software project, within a software organization. It consists of a detailed plan describing how to develop, maintain, replace and alter or enhance specific software. The life cycle defines a methodology for improving the quality of software and the overall development process.
The following figure is a graphical representation of the various stages of a typical SDLC.
A typical Software Development Life Cycle consists of the following stages −
Stage 1: Planning and Requirement Analysis
Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas.
Planning for the quality assurance requirements and identification of the risks associated with the project is also done in the planning stage. The outcome of the technical feasibility study is to define the various technical approaches that can be followed to implement the project successfully with minimum risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to clearly define and document the product requirements and get them approved from the customer or the market analysts. This is done through an SRS (Software Requirement Specification) document which consists of all the product requirements to be designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
SRS is the reference for product architects to come out with the best architecture for the product to be developed. Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification.
This DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules (if any). The internal design of all the modules of the proposed architecture should be clearly defined with the minutest of the details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle.
Developers must follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers, etc. are used to generate the code. Different high level programming languages such as C, C++, Pascal, Java and PHP are used for coding. The programming language is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the product where product defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.
Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometimes product deployment happens in stages as per the business strategy of that organization. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.Video link:Embedded video link:Link: https://projects.invisionapp.com/d/main#/console/20294675/458743820/preview
SDLC is a process followed for a software project, within a software organization. It consists of a detailed plan describing how to develop, maintain, replace and alter or enhance specific software. The life cycle defines a methodology for improving the quality of software and the overall development process.
The following figure is a graphical representation of the various stages of a typical SDLC.
A typical Software Development Life Cycle consists of the following stages −
Stage 1: Planning and Requirement Analysis
Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas.
Planning for the quality assurance requirements and identification of the risks associated with the project is also done in the planning stage. The outcome of the technical feasibility study is to define the various technical approaches that can be followed to implement the project successfully with minimum risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to clearly define and document the product requirements and get them approved from the customer or the market analysts. This is done through an SRS (Software Requirement Specification) document which consists of all the product requirements to be designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
SRS is the reference for product architects to come out with the best architecture for the product to be developed. Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification.
This DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules (if any). The internal design of all the modules of the proposed architecture should be clearly defined with the minutest of the details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle.
Developers must follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers, etc. are used to generate the code. Different high level programming languages such as C, C++, Pascal, Java and PHP are used for coding. The programming language is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the product where product defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.
Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometimes product deployment happens in stages as per the business strategy of that organization. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.Video link:Embedded video link:Link: https://projects.invisionapp.com/d/main#/console/20294675/458743820/preview
Authored by: Vijayalaxmi vishvanath mali
Navigating Context
Posted on: #iteachmsu
By Shravya: Tips for using a collaboration software tool -- edited
When project managing a distributed team in a variety of locations, a collaboration software (or project management) tool is an effective way to keep everyone on the same page and all of your project information in one place. However, using a great tool doesn’t magically make collaboration happen. Here are 10 best practices when using a collaboration software tool:
Share proactively - Assign team members to the tasks they need to be aware of and @mention them in the comments, so they receive alerts when the ball is in their court.
Put every project into your collaboration project management tool - Use your tool as a single source of all project-related materials and notes. This will make the material easy to find for everyone, no matter when they joined the project.
Create water cooler channels - Creating channels in your communication tools where team members can discuss non-work related topics allows them to get to know each other and be social even from afar.
Celebrate small wins - Collaboration tools are a great place to share victories, no matter how big or small. Even a short message can go a long way.
Balance the load - You can’t collaborate well if you’re overloaded with work. Use your tool’s visibility and resource management features to ensure project tasks are balanced among your team members.
Share proactively - Assign team members to the tasks they need to be aware of and @mention them in the comments, so they receive alerts when the ball is in their court.
Put every project into your collaboration project management tool - Use your tool as a single source of all project-related materials and notes. This will make the material easy to find for everyone, no matter when they joined the project.
Create water cooler channels - Creating channels in your communication tools where team members can discuss non-work related topics allows them to get to know each other and be social even from afar.
Celebrate small wins - Collaboration tools are a great place to share victories, no matter how big or small. Even a short message can go a long way.
Balance the load - You can’t collaborate well if you’re overloaded with work. Use your tool’s visibility and resource management features to ensure project tasks are balanced among your team members.
Authored by: Vijaya
Disciplinary Content
Posted on: #iteachmsu

Graphical user interface
graphical user interface:
The graphical user interface (GUI is a form of user interface that allows users to interact with electronic devices through graphical icons and audio indicators such as primary notation, instead of text-based user interfaces, typed command labels, or text navigation. GUIs were introduced in reaction to the perceived steep learning curve of command-line interfaces (CLIs), which require commands to be typed on a computer keyboard.
The actions in a GUI are usually performed through direct manipulation of the graphical elements. Beyond computers, GUIs are used in many handheld mobile devices such as MP3 players, portable media players, gaming devices, smartphones, and smaller household, office, and industrial controls. The term GUI tends not to be applied to other lower-display resolution types of interfaces, such as video games ), or not including flat screens, like volumetric displays.
User interface and interaction design:
Designing the visual composition and temporal behavior of a GUI is an important part of software application programming in the area of human-computer interaction. Its goal is to enhance the efficiency and ease of use for the underlying logical design of a stored program, a design discipline named usability. Methods of user-centered design are used to ensure that the visual language introduced in the design is well-tailored to the tasks.
The visible graphical interface features of an application are sometimes referred to as chrome or GUI (pronounced gooey) Typically, users interact with information by manipulating visual widgets that allow for interactions appropriate to the kind of data they hold. The widgets of a well-designed interface are selected to support the actions necessary to achieve the goals of users.
The graphical user interface (GUI is a form of user interface that allows users to interact with electronic devices through graphical icons and audio indicators such as primary notation, instead of text-based user interfaces, typed command labels, or text navigation. GUIs were introduced in reaction to the perceived steep learning curve of command-line interfaces (CLIs), which require commands to be typed on a computer keyboard.
The actions in a GUI are usually performed through direct manipulation of the graphical elements. Beyond computers, GUIs are used in many handheld mobile devices such as MP3 players, portable media players, gaming devices, smartphones, and smaller household, office, and industrial controls. The term GUI tends not to be applied to other lower-display resolution types of interfaces, such as video games ), or not including flat screens, like volumetric displays.
User interface and interaction design:
Designing the visual composition and temporal behavior of a GUI is an important part of software application programming in the area of human-computer interaction. Its goal is to enhance the efficiency and ease of use for the underlying logical design of a stored program, a design discipline named usability. Methods of user-centered design are used to ensure that the visual language introduced in the design is well-tailored to the tasks.
The visible graphical interface features of an application are sometimes referred to as chrome or GUI (pronounced gooey) Typically, users interact with information by manipulating visual widgets that allow for interactions appropriate to the kind of data they hold. The widgets of a well-designed interface are selected to support the actions necessary to achieve the goals of users.
Authored by: Rupali
Posted on: #iteachmsu
Article : internationally recognized certificate serves as proof of performance, strengthening both
https://www.bankrate.com/investing/stock-market-basics-for-beginners/Software testing is governed by seven principles:Absence of errors fallacy: Even if the software is 99% bug-free, it is unusable if it does not conform to the user's requirements. Software needs to be bug-free 99% of the time, and it must also meet all customer requirements.Testing shows the presence of errors: Testing can verify the presence of defects in software, but it cannot guarantee that the software is defect-free. Testing can minimize the number of defects, but it can't remove them all.Exhaustive testing is not possible: The software cannot be tested exhaustively, which means all possible test cases cannot be covered. Testing can only be done with a select few test cases, and it's assumed that the software will produce the right output in all cases. Taking the software through every test case will cost more, take more effort, etc., which makes it impractical.Defect clustering: The majority of defects are typically found in a small number of modules in a project. According to the Pareto Principle, 80% of software defects arise from 20% of modules.Pesticide Paradox: It is impossible to find new bugs by re-running the same test cases over and over again. Thus, updating or adding new test cases is necessary in order to find new bugs.Early testing: Early testing is crucial to finding the defect in the software. In the early stages of SDLC, defects will be detected more easily and at a lower cost. Software testing should start at the initial phase of software development, which is the requirement analysis phase.Testing is context-dependent: The testing approach varies depending on the software development context. Software needs to be tested differently depending on its type. For instance, an ed-tech site is tested differently than an Android app.
Posted by: Super Admin
Disciplinary Content
Posted on: #iteachmsu

SDLC Models
There are various software development life cycle models defined and designed which are followed during the software development process. These models are also referred as Software Development Process Models". Each process model follows a Series of steps unique to its type to ensure success in the process of software development.
Following are the most important and popular SDLC models followed in the industry −
Waterfall Model
Iterative Model
Spiral Model
V-Model
Big Bang Model
Other related methodologies are Agile Model, RAD Model, Rapid Application Development and Prototyping Models.Embedded video link:
Following are the most important and popular SDLC models followed in the industry −
Waterfall Model
Iterative Model
Spiral Model
V-Model
Big Bang Model
Other related methodologies are Agile Model, RAD Model, Rapid Application Development and Prototyping Models.Embedded video link:
Authored by: Vijayalaxmi mhetre
Disciplinary Content
Posted on: What are the 12 Agi...
The Agile Alliance defines 12 lightness principles for those who need to attain agility: Our highes
Edited: The Agile Alliance defines 12 lightness principles for those who need to attain agility:
Our highest priority is to satisfy the client through early and continuous delivery of valuable computer software.
Welcome dynamic necessities, even late in development. Agile Processes harness modification for the customer’s competitive advantage.
Deliver operating computer software often, from a pair of weeks to a couple of months, with a preference to the shorter timescale.
Business individuals and developers should work along daily throughout the project.
The build comes around actuated people. offer them the setting and support they have, and trust them to urge the task done.
the foremost economical and effective methodology of conveyancing info to and among a development team is face-to-face speech.
Working with computer software is the primary life of progress.
Agile processes promote property development. The sponsors, developers, and users will be able to maintain a relentless pace indefinitely.
Continuous attention to technical excellence and smart style enhances nimbleness.
Simplicity—the art of maximizing the number of work not done—is essential.
the most effective architectures, necessities, and styles emerge from self–organizing groups.
At regular intervals, the team reflects on a way to become simpler, then tunes and adjusts its behavior consequently.
Our highest priority is to satisfy the client through early and continuous delivery of valuable computer software.
Welcome dynamic necessities, even late in development. Agile Processes harness modification for the customer’s competitive advantage.
Deliver operating computer software often, from a pair of weeks to a couple of months, with a preference to the shorter timescale.
Business individuals and developers should work along daily throughout the project.
The build comes around actuated people. offer them the setting and support they have, and trust them to urge the task done.
the foremost economical and effective methodology of conveyancing info to and among a development team is face-to-face speech.
Working with computer software is the primary life of progress.
Agile processes promote property development. The sponsors, developers, and users will be able to maintain a relentless pace indefinitely.
Continuous attention to technical excellence and smart style enhances nimbleness.
Simplicity—the art of maximizing the number of work not done—is essential.
the most effective architectures, necessities, and styles emerge from self–organizing groups.
At regular intervals, the team reflects on a way to become simpler, then tunes and adjusts its behavior consequently.
Posted by: Chathuri Super admin..
Disciplinary Content
Posted on: #iteachmsu

computer science
Computer science focuses on the development and testing of software and software systems. It involves working with mathematical models, data analysis and security, algorithms, and computational theory. Computer scientists define the computational principles that are the basis of all software.
Posted by: Super Admin
Posted on: #iteachmsu

Computer Science
Computer science is the study of computers and computational systems. It is a broad field which includes everything from the algorithms that make up software to how software interacts with hardware to how well software is developed and designed.
Some common job titles for computer scientists include:
Computer Programmer
Information Technology Specialist
Data Scientist
Web Optimization Specialist
Database Administrator
Systems Analyst
Web Developer
https://projects.invisionapp.com/d/main?origin=v7#/console/20294675/474484363/inspect
Some common job titles for computer scientists include:
Computer Programmer
Information Technology Specialist
Data Scientist
Web Optimization Specialist
Database Administrator
Systems Analyst
Web Developer
https://projects.invisionapp.com/d/main?origin=v7#/console/20294675/474484363/inspect
Authored by: Shweta
Assessing Learning
Posted on: #iteachmsu

Software-as-a-Service (SaaS) is a software licensing model in which access to the software is provided on a subscription basis, with the software being located on external servers rather than on servers located in-house. Software-as-a-Service is typically accessed through a web browser, with users logging into the system using a username and password.
Posted by: Rupali Jagtap
Assessing Learning
Posted on: #iteachmsu
The uses of formal methods for software and hardware design is motivated by the expectation that, as in other engineering disciplines, performing the appropriate mathematical analysis can contribute to the reliability and robustness of a design. They form an important theoretical underpinning for software engineering, especially where safety or security is involved. Formal methods are a useful adjunct to software testing since they help avoid errors and can also give a framework for testing. For industrial use, tool support is required. However, the high cost of using formal methods means that they are usually only used in the development of high-integrity and life-critical systems, where safety or security is of utmost importance. Formal methods are a particular kind of mathematically based technique for the specification, development, and verification of software and hardware systems.[46] The use of formal methods for software and hardware design is motivated by the expectation that, as in other engineering disciplines, performing the appropriate mathematical analysis can contribute to the reliability and robustness of a design.
Posted by: Rupali Jagtap
Assessing Learning
Posted on: #iteachmsu
Android software development is the process by which applications are created for devices running the Android operating system. Google states that "Android apps can be written using Kotlin, Java, and C++ languages" using the Android software development kit (SDK), while using other languages is also possible.
Posted by: Chathuri Super admin..
Posted on: What are the 12 Agi...

Edited: The Agile Alliance defines 12 lightness principles for those who need to attain agility:
Our highest priority is to satisfy the client through early and continuous delivery of valuable computer software.
Welcome dynamic necessities, even late in development. Agile Processes harness modification for the customer’s competitive advantage.
Deliver operating computer software often, from a pair of weeks to a couple of months, with a preference to the shorter timescale.
Business individuals and developers should work along daily throughout the project.
The build comes around actuated people. offer them the setting and support they have, and trust them to urge the task done.
the foremost economical and effective methodology of conveyancing info to and among a development team is face-to-face speech.
Working with computer software is the primary life of progress.
Agile processes promote property development. The sponsors, developers, and users will be able to maintain a relentless pace indefinitely.
Continuous attention to technical excellence and smart style enhances nimbleness.
Simplicity—the art of maximizing the number of work not done—is essential.
the most effective architectures, necessities, and styles emerge from self–organizing groups.
At regular intervals, the team reflects on a way to become simpler, then tunes and adjusts its behavior consequently.
Our highest priority is to satisfy the client through early and continuous delivery of valuable computer software.
Welcome dynamic necessities, even late in development. Agile Processes harness modification for the customer’s competitive advantage.
Deliver operating computer software often, from a pair of weeks to a couple of months, with a preference to the shorter timescale.
Business individuals and developers should work along daily throughout the project.
The build comes around actuated people. offer them the setting and support they have, and trust them to urge the task done.
the foremost economical and effective methodology of conveyancing info to and among a development team is face-to-face speech.
Working with computer software is the primary life of progress.
Agile processes promote property development. The sponsors, developers, and users will be able to maintain a relentless pace indefinitely.
Continuous attention to technical excellence and smart style enhances nimbleness.
Simplicity—the art of maximizing the number of work not done—is essential.
the most effective architectures, necessities, and styles emerge from self–organizing groups.
At regular intervals, the team reflects on a way to become simpler, then tunes and adjusts its behavior consequently.
Posted by: Chathuri Super admin..
Assessing Learning
Posted on: #iteachmsu
Edited: The Agile Alliance defines 12 lightness principles for those who need to attain agility:
Our highest priority is to satisfy the client through early and continuous delivery of valuable computer software.
Welcome dynamic necessities, even late in development. Agile Processes harness modification for the customer’s competitive advantage.
Deliver operating computer software often, from a pair of weeks to a couple of months, with a preference to the shorter timescale.
Business individuals and developers should work along daily throughout the project.
The build comes around actuated people. offer them the setting and support they have, and trust them to urge the task done.
the foremost economical and effective methodology of conveyancing info to and among a development team is face-to-face speech.
Working with computer software is the primary life of progress.
Agile processes promote property development. The sponsors, developers, and users will be able to maintain a relentless pace indefinitely.
Continuous attention to technical excellence and smart style enhances nimbleness.
Simplicity—the art of maximizing the number of work not done—is essential.
the most effective architectures, necessities, and styles emerge from self–organizing groups.
At regular intervals, the team reflects on a way to become simpler, then tunes and adjusts its behavior consequently.
Our highest priority is to satisfy the client through early and continuous delivery of valuable computer software.
Welcome dynamic necessities, even late in development. Agile Processes harness modification for the customer’s competitive advantage.
Deliver operating computer software often, from a pair of weeks to a couple of months, with a preference to the shorter timescale.
Business individuals and developers should work along daily throughout the project.
The build comes around actuated people. offer them the setting and support they have, and trust them to urge the task done.
the foremost economical and effective methodology of conveyancing info to and among a development team is face-to-face speech.
Working with computer software is the primary life of progress.
Agile processes promote property development. The sponsors, developers, and users will be able to maintain a relentless pace indefinitely.
Continuous attention to technical excellence and smart style enhances nimbleness.
Simplicity—the art of maximizing the number of work not done—is essential.
the most effective architectures, necessities, and styles emerge from self–organizing groups.
At regular intervals, the team reflects on a way to become simpler, then tunes and adjusts its behavior consequently.
Posted by: Chathuri Super admin..
Justice and Belonging
Posted on: #iteachmsu

Stage 1: Planning and Requirement Analysis
Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas.
Planning for the quality assurance requirements and identification of the risks associated with the project is also done in the planning stage. The outcome of the technical feasibility study is to define the various technical approaches that can be followed to implement the project successfully with minimum risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to clearly define and document the product requirements and get them approved from the customer or the market analysts. This is done through an SRS (Software Requirement Specification) document which consists of all the product requirements to be designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
SRS is the reference for product architects to come out with the best architecture for the product to be developed. Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification.
This DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules (if any). The internal design of all the modules of the proposed architecture should be clearly defined with the minutest of the details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle.
Developers must follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers, etc. are used to generate the code. Different high level programming languages such as C, C++, Pascal, Java and PHP are used for coding. The programming language is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the product where product defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.
Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometimes product deployment happens in stages as per the business strategy of that organization. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.
Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas.
Planning for the quality assurance requirements and identification of the risks associated with the project is also done in the planning stage. The outcome of the technical feasibility study is to define the various technical approaches that can be followed to implement the project successfully with minimum risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to clearly define and document the product requirements and get them approved from the customer or the market analysts. This is done through an SRS (Software Requirement Specification) document which consists of all the product requirements to be designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
SRS is the reference for product architects to come out with the best architecture for the product to be developed. Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification.
This DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules (if any). The internal design of all the modules of the proposed architecture should be clearly defined with the minutest of the details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle.
Developers must follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers, etc. are used to generate the code. Different high level programming languages such as C, C++, Pascal, Java and PHP are used for coding. The programming language is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the product where product defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.
Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometimes product deployment happens in stages as per the business strategy of that organization. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.
Posted by: Super Admin
Disciplinary Content
Posted on: #iteachmsu
Concordion is a powerful tool, written in Java, that is used to write and manage automated acceptance tests. It is distributed under the Apache Software License. Its clean and simple concepts make it very easy to learn and use. Concordion can be used along with .NET, Python, Fantom, Scala, and Ruby languages. test by 935
Posted by: Super Admin
Posted on: #iteachmsu
Concordion is a powerful tool, written in Java, that is used to write and manage automated acceptance tests. It is distributed under the Apache Software License. Its clean and simple concepts make it very easy to learn and use. Concordion can be used along with .NET, Python, Fantom, Scala, and Ruby languages. test by 935
Posted by: Super Admin
Host: MSU Libraries
3D Terrain Elevation Models for 3D Printing (Online)
Learn how to produce a 3D model of terrain elevation for printing on a 3D printer. We will learn about 3D models for 3D printing, digital elevation models (DEMs), where to find DEM data to create our printable export, and then use a plug in DEMto3D in the open source software QGIS to create a model. If time allows, basic tools for 3D model editing in Meshmixer or slicing software will be demonstrated.
Navigating Context
Host: MSU Libraries
Learn QGIS: Making a color shaded map in QGIS (Online)
Learn the basics of QGIS, the free open-source geospatial software—this workshop will demonstrate how to make a choropleth (color shaded) map and place graduated symbols representing data on it, load shape-files and .csv table files into QGIS, join data to spatial information and edit features. No experience with QGIS or Geographic Information Systems is required.
Navigating Context
Host: MSU Libraries
Zotero Workshop (Online)
An introduction to the free open source citation management program Zotero. In this workshop, participants will learn how to:
Download references from MSU's article databases and websites
Format citations and bibliographies in a Word document
Create groups and share references with other users
Registration for this event is required.
You will receive a link to join a Zoom meeting before the workshop. Please install the Zotero software and Zotero browser connector on your computer before the session begins. More information is available from https://libguides.lib.msu.edu/zotero/setup.
Questions or need more information? Contact the MSU Libraries Zotero training team at lib.dl.zotero@msu.edu.
To schedule a separate session for your class or research group, please contact the Zotero team at lib.dl.zotero@msu.edu.
Navigating Context
Host: #iteachmsu

Computer Fundamentals
Computer is an advanced electronic device that takes raw data as an input from the user and processes it under the control of a set of instructions (called program), produces a result (output), and saves it for future use. This tutorial explains the foundational concepts of computer hardware, software, operating systems, peripherals, etc. along with how to get the most value and impact from computer technology.