How to Gets or sets the fully qualified path of the current working directory.
How to get Application Data folder:-
How to get current application name:-
How to download a file (zip) from a url/web service (php) using c#
- WebClient oWebClient = new WebClient();
How to extract zip file using c#.net (till Framework 4.0)
Use a third party library (SharpZipLib)
- FastZip oFastZip = new FastZip();
How to replace a string in an string array in c#
- var values = line.Split(‘,’);
- var sanatizedValues = values.Select(x => x == “” ? x : “Null”).ToArray(); OR
string items2 = items.Select(x => x.Replace(“one”, “zero”)).ToArray();
Despite the currently most selling brand in Pakistan. Q- Mobile is very low in quality and hardly completes its warranty period. You will be lucky if it dies sooner so you can claim your warranty.
I have used Nokia and there is a marginal difference between the quality of Nokia products and Q-Mobile. Recently my Q-mobile A9 losses it touch sensitivity making it a complete dump. I can’t even retrieve any data within the phone.
Beware before buying Q-mobile specially touch screen. It’s better if you try out a low specification HTC mobile. It will be more durable as compared to your so called brand new Q-mobile.
I have even used Q-mobile with key pad they aren’t even comparable to Nokia mobile. They do provide a bit more features but the quality of Camera, Keypad and Mic is very low. So you have to change your mobile within very short span of time.
Ashfaq Memorial Hospitals Telephone Number
- Dr Tariquee:- 5:30-6:30PM (Monday-Saturday)
- Dr Qaisar Sajjad: 6:30-7:30PM (Monday-Saturday)
- Perven Azam
Note:- If you are still looking for any other doctor bill do mention it in comment box. I will add that to the list as well. Also if you have some knowledge about any other doctors timing do mention it here.
The structure of business analysis documents isn’t a commonly discussed topic. This article will show what documents are produced by a BA and the main sections they contain.
These are the main documents produced by a BA over the course of a project:
- Current state analysis document
- Project vision document
- Solution vision document
- Business requirements document
- Business process design document
- Use case model document
- Use case specification document
- System-wide requirements document
- Solution glossary
The diagram below shows the attributes common to all documents:
Current State Analysis
Once a project has been mandated and the Project Initiation document (PID) is drafted, a business analyst can start to work on requirements gathering. In my experience the best way to tackle this task is to start from current state analysis. It helps understand the business need, primary pain points, business processes affected, the stakeholders involved in these processes, and so on.
The area of the current state analysis is illustrated below:
The main purpose of the analysis is to present the “AS IS” state: the existing business context, background, business functions and existing business processes, and finally stakeholders involved in these business processes. Depending on the project nature, some components of the underlying infrastructure can be included in the document as well.
A Current State Analysis document lists the key pain points within the identified business processes and tasks within them, and highlights the areas where a change is expected.
The last section of the document is about presenting recommendations. It recaps the key findings and lists the key changes expected. Any caveats should be presented here as well.
The content structure of the Current State Analysis document is presented below:
This document serves as a foundation or a reference point for other artifacts produced by a business analyst. The other documents will be discussed in the following articles.
The Project Vision is a document which is shared by a project manager and business analyst. They work together to outline the problem statement, determine the desired state, describe the criteria of business acceptance of the deliverables and how project success will be measured. The document contains a section with stakeholder analysis which shows all the parties involved along with their responsibilities and needs:
The business analyst adds the high level requirements which are within the scope of the project, and marks each requirement as compulsory or optional. To clearly define the project scope and avoid ambiguity, all out-of-scope requirements are also listed at the end of the section.
Based on the results of the current state analysis the business analyst describes the current business context, the key business processes and services used to support them. After that the required changes are mapped to the current business context. It can be a good idea to present this mapping as a diagram for easy communication of the proposed changes to the business stakeholders.
Once the Project Vision document is approved, the preparation of the Solution Vision document starts.
First, the business analyst recaps the problem statement from the Project Vision artifact. The solution statement describes the target audience of the solution, what will be satisfied by the solution and what the key benefits will be. The statement of differentiation of the solution from possible alternative options is added as a conclusive point in positioning of the solution.
The document describes stakeholders within the target audience along with their roles using a RACI matrix.
The main part of a Solution Vision is a detailed section devoted to the solution capabilities comprised of both functional and non-functional features, with priorities given by the business stakeholders.
The next section presents the business context in its future “to be” state. It’s a good idea to include a a diagram illustrating the key changes and additions to the existing state, as well as a brief narrative to clarify the proposed changes.
Similarly to the Project Vision document, the features that are out of scope are clearly listedin the last section to make sure everyone is on the same page with regards to what will be implemented.
This document focuses on providing details about the current processes and gives enough information to describe the business problem and how it fits into the scope of the project. This section reiterates the findings of the Current State Analysis document, however here they are aligned with the project objectives.
The business requirements that are going to be fulfilled by the solution are listed in the “In Scope” section. Business rules that apply to the described requirements are presented in a separate section. This approach simplifies the confirmation of the rules with business stakeholders.
Any assumptions and dependencies identified in relation to the business requirements are to be listed in the appropriate section.
The proposed changes to stakeholder roles, new or modified business processes and business services that support them are presented in the last section.
Business Process Design
This document focuses on the scope of changes to business processes, providing details about the current business context, existing business processes, and stakeholders involved in these business processes.
It also describes the future state: the proposed business processes and the “to be” information environment. The new processes are accompanied with narratives to facilitate communication of the proposed changes to stakeholders and business end users. This “as is” section reiterates the findings of the Current State Analysis document, however here they are aligned with the changes to supporting business services.
Any assumptions and dependencies identified in relation to changes to the business processes are listed in the appropriate section.
Use Case Model
The Use Case Model lists all the scenarios for using the solution required by the business stakeholders. It is useful to describe the solution as a set of functional areas and group the scenarios per functional area. Such an approach allows to use this document more efficiently in communication with the business stakeholders as they can easily refer to the sections of their interest.
The model lists all possible scenarios in scope, their brief summary, actors involved in each scenario, frequency of use, triggering events and the two possible outcomes – success and failure.
One of the key attributes of the scenarios is a reference to the high-level requirements and required capabilities which allows to establish traceability.
Note: when making changes to Use Case Specifications, do not forget to update the Use Case Model document accordingly.
Use Case Specification
A Use Case Specification document presents more detailed information about the use cases in the Use Case Model document.
Each specification includes:
- Brief use case overview
- Reference to the functional area
- Actors involved
- Main flow
- Alternative flows
- Exception handling flows
- Functional requirements for the solution
- Traceability to the business requirements
- Market or business rules applicable to the scenario
- User interface, controls and data
This document is prepared when the Business Requirements, Use Case Model and Use Case Specifications are complete. The main purpose of the document is to present a “qualitative” side of the solution.
The “Load patterns” section is the most interesting as it illustrates how the solution is expected to be used during a business day. This information gives good insight into business requirements from the “non-functional” perspective and helps clarify the business requirements where required.As solutions are often based on information technology, some attention should be given to solution resilience. Disaster mitigation approaches and solution recovery requirements play a major role here.It is a rare case nowadays that a solution is completely new. The common practice is to integrate the solution into the existing business environment. The system-wide requirements document describes the interfaces with internal and external systems and solutions, the data flowing between them, its formats and data elements. Where the solution should interface with external systems, samples of data must be presented in appendices.Apart from business reporting capabilities, the solution must provide reporting capabilities for monitoring how the solution operates. These reports are listed in the last section of the document.
Business stakeholders often use terms and jargon in their communication. To get up to speed with this terminology (you can be quite new to it), the Solution Glossary document is used. It helps establish common terminology for the project team and key stakeholders, and for use within the solution. The structure of this document is simple:
It’s a good practice to divide the solution into functional areas. These functional areas serve as small knowledge domains for the stakeholders involved in the project. This document serves as a reference point for all the previously discussed documents.
Recently I faced any issue where after restoring the database in mysql, auto increment values started from zero.
This started giving duplicated entry error. First I figured out the issue using this
SELECT AUTO_INCREMENT FROM information_schema.tables
WHERE table_schema=’mydb’ AND table_name=’mytablename’
Then I tried to resolve this using:-
SET AUTO_INCREMENT = 13565
WHERE table_schema=’mydb’ AND table_name=’mytablename’
But got error mentioning:-
Access denied for user ‘root’@’localhost’ to database ‘information_schema’
ALTER TABLE mytable AUTO_INCREMENT = 0
will reset the auto_increment value to be the next value based on the highest existing value in the auto_increment column.
The web server process that was being debugged has been terminated by Internet Information Services (IIS)
Run –> inetmgr –> enter –> click on App Pool -> right-click on App –> set Application Pool Defaults –> just change everything with (seconds) to 600 instead of 90.
When you are debugging, IIS will not service any other requests until you are done stepping through your code. That includes the “ping” request that IIS sends to itself. Since IIS doesn’t hear back from itself, it decides to shut itself down, which promptly terminates your debugging.
The solution is to increase the Ping Maximum Response Time in the application pool settings from its default value of 90 seconds. Set it to something high enough that will give you enough time to debug your code (like maybe 600 seconds).
Microsoft has a long-winded write-up here, or you can just look at the pretty picture.
Edit: Others have suggested setting “Ping Enabled” to false. There are several reasons why I prefer to keep it in place, just with a larger interval, but the most important is that you will (most likely) have worker processing pinging enabled on production, and you should strive to develop and debug under a configuration that is as close to production as possible. If you do NOT have ping enabled on production, then by all means disable it locally as well.
I have a few projects in subversion using the same set of third party tools nant, bdd, mbunit etc. I’ve read its a good idea to put the tools into their own repository and include them in the other projects using an svn:external. The advantage this gives you is any changes you make to the external repository can be updated easily across all projects. Any hoose this is who to do it.
Go to the root of the folder you want to add the externals too.
Select svn:externals from the property name drop down list.
Enter the name you want to give to the external folder followed by the path to your tools repository in property value text area.
In the example above: tools svn://server/tools/trunk
Note: You can add more external repositories by simply adding more lines to the property value text area.
Right click on the root folder and select SVN Update from the menu. Subversion will now pull down the files from the external repository and your done.
Once you check this change in other people checking out from the repository will automatically get the externals folder. Also any changes to the external repository will be updated in this repository on any update. So in this case if I add a new tool or update one of the tools all repositories using this external repository will get the changes on their next update.
Don’t forget to give the folder name before the repository address and not just the repository address or you will get an error along the lines of: Error parsing svn:externals property on …
Copied from :-